Master Reference

Rebrand Copy Rules

If the transition reference is needed during the first 1–2 months, place it above the hero headline as a clean one-line statement:

Superior Biz Solutions is now Nearby.

Then lead straight into the hero. After the transition period (approx. 2 months post full launch), this line gets removed entirely.

Sales & Marketing

Customer Experience

Operations & Admin

Finance & Accounting

Brand & Creative

E-Commerce

Technology

Header

[nearby logo]  How It Works  Hire ▼  Why Nearby ▼  Resources ▼  [Get Started →]

Every L2+ page gets a visible breadcrumb and BreadcrumbList JSON-LD.

1. Every role page → parent category page
2. Every role page → 2–3 related roles ("You might also need...")
3. Every role page → /contact
4. Every blog post → at least 1 role page
5. /why-nearby/latam-talent → top role pages across all 7 categories
6. /why-nearby/client-stories → role pages matching each client’s use case
7. /resources/calculator → role pages by category
8. No page more than 3 clicks from homepage
9. No orphan pages at launch

Cross-Category Examples

• /hire/ecommerce/amazon-marketplace-manager → /hire/brand-creative/amazon-a-plus-designer
• /hire/technology/web-developer → /hire/brand-creative/ux-ui-designer
• /for/fashion-apparel → /hire/brand-creative/fashion-designer + /hire/brand-creative/tech-pack-designer

Index at nearby.team/sitemap.xml pointing to 4 child sitemaps. Never include noindex pages in the sitemap.

User-agent: *
Disallow: /hire/brief
Disallow: /hire/submit
Disallow: /thank-you
Disallow: /talent/
Disallow: /for/
Disallow: /compare/

Sitemap: https://nearby.team/sitemap.xml

<link rel="canonical" href="https://nearby.team/hire/brand-creative/fashion-designer" />

Limits: Title 60 chars max · Description 155 chars max · Every page unique.

One H1 per page. No exceptions.

Role page:
H1: Hire a Remote [Role] | LATAM Talent Starting from $[RATE]/hr
  H2: What Your [Role] Will Handle
  H2: Skills & Tools
  H2: What Nearby Manages Behind the Hire
  H2: Frequently Asked Questions
    H3: [Each FAQ question]

Category page:
H1: Hire Remote [Category] Professionals
  H2: Roles We Place
    H3: [Each role card title]
  H2: What’s Included With Every Nearby Hire

<meta property="og:type" content="website" />
<meta property="og:site_name" content="Nearby" />
<meta property="og:title" content="[Page Title]" />
<meta property="og:description" content="[Page Description]" />
<meta property="og:url" content="https://nearby.team/[path]" />
<meta property="og:image" content="https://nearby.team/images/og/[slug].jpg" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />
<meta name="twitter:card" content="summary_large_image" />

OG Images Required at Launch (1200×630px JPG)

• og-default.jpg — homepage / fallback
• og-hire.jpg — /hire hub
• One per category: og-sales-marketing.jpg, og-customer-experience.jpg, og-operations-admin.jpg, og-finance-accounting.jpg, og-brand-creative.jpg, og-ecommerce.jpg, og-technology.jpg
• og-blog.jpg — blog default

Role-level OG images → Phase 2.

Phase 1: April 20 — SBS Hero Page (no redirect)

The SBS domain does NOT redirect on April 20. The site is stripped to a single hero section with one message and one CTA.

superiorbizsolutions.com homepage:
  H1: "Superior Biz Solutions is now Nearby."
  CTA Button: "Take me there →"  [links to nearby.team]
  Nothing else. No nav. No paragraphs. No explanation.

Phase 2: ~September 2026 — 301 Redirect Activates

Approximately 2 months after the full marketing launch, once traffic has naturally migrated. All redirects: 301 (permanent). Server/CDN level — not JS or meta refresh. Never chain redirects.

Submit GSC change of address (superiorbizsolutions.com → nearby.team) after 301 activates. Audit for redirect chains 30 days post-activation.

YouTube Shorts Embed Container (mandatory — prevents CLS)

<div style="position:relative;padding-bottom:177.78%;height:0;overflow:hidden;">
  <iframe src="https://www.youtube.com/embed/[VIDEO_ID]"
    style="position:absolute;top:0;left:0;width:100%;height:100%;"
    frameborder="0" allowfullscreen loading="lazy">
  </iframe>
</div>

Hero Image (prevents LCP failure)

<link rel="preload" as="image" href="/images/hero.jpg" />
<img src="/images/hero.jpg" fetchpriority="high" alt="..." width="1440" height="640" />

• Alt text: Describe what the image shows. No keyword stuffing.
• File names: Descriptive, hyphenated, lowercase. Good: remote-bookkeeper-latin-america.jpg
• Format: WebP preferred (30–50% smaller than JPG). JPG fallback.
• Compression: Under 200KB content images · Under 100KB thumbnails.
• Hero images: fetchpriority="high" + preload in <head>. Never lazy-load.
• All images: Must have explicit width and height attributes to prevent CLS.

Use both robots.txt AND meta robots on excluded pages.

<!-- Transactional pages — permanent noindex -->
<meta name="robots" content="noindex, nofollow" />

<!-- Phase 2 pages until launched -->
<meta name="robots" content="noindex, follow" />

noindex, follow = Google won’t index but follows internal links. Link equity flows. Safer than nofollow.

• HTTPS on all pages. HTTP → HTTPS at server level (not JS).
• SSL auto-renewal configured.
• HSTS header: Strict-Transport-Security: max-age=31536000; includeSubDomains

Full Launch Day

• Verify nearby.team property
• Submit https://nearby.team/sitemap.xml
• Request indexing: homepage + one role page per category (7 total)
• Set preferred domain (non-www)
• Confirm all SBS redirect domains resolve correctly

Week 2

• Coverage report — flag crawl errors
• Core Web Vitals report — flag LCP/CLS failures
• Confirm breadcrumbs parsed (Enhancements → Breadcrumbs)
• Confirm FAQ rich snippets parsed (Enhancements → FAQs)

Avoid shared hosting (GoDaddy, Bluehost) — TTFB will fail LCP targets on mobile.

Custom 404 required at launch. Must include:

• "This page doesn’t exist" message
• Link to homepage
• Link to /hire hub
• Same header and footer as the rest of the site

The talent showcase is Phase 2. It lives at /talent/ and is noindex until Phase 2 conditions are met. It is a separate section from the main /hire/* architecture — different purpose, different buyer stage. /hire is for decision-stage buyers. /talent is for consideration-stage buyers who want to see who they’re hiring before committing to a conversation.

URL Structure — 7 Categories

Essential vs Specialized — Role Classification

Each category has two tiers. Essential roles = any business in that category will hire these. Specialized roles = require more specific context, seniority, or tool expertise.

Role Page URL Structure

/talent/[category]/[role-slug]

Examples:
/talent/brand-creative/graphic-designer
/talent/brand-creative/fashion-designer
/talent/finance-accounting/bookkeeper
/talent/technology/frontend-developer

Content Template — Category Hub Page

Content Template — Individual Role Page

Phase 2 Unlock Conditions per Category

ALL conditions must be true before a category page goes live. Partial launches are worse than no launch.

Category Copy Summaries

Based on the SBS brand documents, updated to Nearby’s 7-category structure. All "SBS" references updated to "Nearby."