SEO on Build Me Web starts with clear pages, honest metadata, and technical hygiene — not tricks. This guide covers titles and descriptions, indexability, sitemaps, and structured data so launches get found for the queries you actually care about.
Pair this with Core Web Vitals work; speed and stability are ranking and conversion factors, not separate workstreams.
Titles & descriptions
Set a unique title and meta description per page. Keep titles under roughly sixty characters and descriptions under roughly one hundred fifty-five so they display cleanly in results. Include the primary keyword naturally — do not stuff.
Title patterns can include the brand at the end (Page topic — Brand) via site defaults, with per-page overrides for campaigns. Descriptions should promise a concrete outcome and invite the click without clickbait.
- Inventory important URLs (Home, money pages, top articles).
- Write titles that differ even when topics are related.
- Align H1 with the title thematically; they need not be identical strings.
- Refresh descriptions when bounce rates from search are high but rankings look fine — the snippet may be the issue.
Home title: Industrial sensors for OEMs — Acme
Home description: Spec-grade sensors with lead times you can plan around.
Talk to engineering about your next line.Preview environments must remain non-indexable so draft titles never compete with production in search.
Indexability
Ensure important pages return 200, are not blocked by robots rules, and are not marked noindex. Soft 404s (200 responses with “not found” content) confuse crawlers — use real 404 status for missing paths.
Canonical tags should point at the preferred host and path. Pagination, filtered listings, and sort parameters often need noindex or canonicals back to a clean listing URL.
- Robots.txt: allow marketing content; disallow private app routes and preview hosts.
- Authentication walls: do not rely on robots alone for confidential content.
- International: use hreflang when you ship true locale variants, not just translated snippets.
After major IA changes, use Search Console URL inspection on a sample of money pages before declaring victory.
Sitemaps
Build Me Web generates XML sitemaps on publish. Submit the sitemap URL in Search Console after launch and whenever you add a large content section (blog, docs, product index).
Sitemaps should list canonical URLs only. Exclude thank-you pages, cart, account, and faceted URLs that should not be indexed. Lastmod dates should update when content meaningfully changes — not on every trivial publish if you can avoid noise.
https://www.example.com/sitemap.xml
├── static pages
├── blog posts
└── product / collection URLs (commerce)Monitor coverage reports weekly for the first month after launch, then on a cadence that matches how often you publish.
Structured data
Use Organization, WebSite, FAQ, Article, and Product schemas where they match visible content. Invalid markup is worse than none — validate before shipping.
FAQ schema belongs only when Q&A is on the page. Product schema must match price and availability. Article schema should reflect author and dates you actually display.
- Unique title + description on every indexable page
- Canonical host chosen and enforced with redirects
- Sitemap submitted and fetched successfully
- Structured data validates for the types you emit
- Preview/staging remain noindex
Troubleshooting
Pages discovered but not indexed: check quality, duplication, and whether the site is brand new with low crawl budget — improve internal links from strong pages.
Wrong snippet: rewrite meta description; ensure the H1 and opening paragraph reinforce the topic.
Product rich results missing: confirm availability and price fields match the visible storefront.
Best practices
Write for humans first. Earn links with useful resources, not schemes. Revisit SEO quarterly with analytics: queries, landing pages, and conversions beat vanity rankings. Keep a shared doc of target queries per money page so design, content, and ads stay aligned.
Prerequisites & preparation
Before changing production settings for SEO fundamentals, align the people who own content, DNS, analytics, and approvals. A fifteen-minute kickoff that names owners prevents multi-day Slack archaeology later. Capture decisions in the workspace notes so the next teammate inherits context instead of guesswork.
Gather credentials and access: workspace admin or editor role, DNS control when hostnames are involved, payment or API sandbox accounts when money paths are involved, and a shared checklist link. Confirm which environment you will rehearse in — preview first, production only after a green run.
List money pages and target queries. Confirm preview stays noindex. Access Search Console for the canonical host.
Detailed walkthrough
Work the happy path slowly the first time. Narrate what you expect to see after each click: a status badge, a DNS record, a webhook delivery, a Lighthouse metric. When reality diverges, stop and resolve the mismatch instead of clicking ahead — most outages begin as ignored yellow states.
- Rewrite titles and descriptions for the top money pages with unique angles.
- Verify robots, canonicals, and status codes on a crawl sample.
- Submit sitemaps and inspect a handful of URLs after publish.
- Add structured data only where visible content supports it; validate.
- Schedule a monthly coverage and query review with content owners.
Edge cases & failure modes
Plan for partial failure. Networks drop, registrars delay, providers rate-limit, and humans approve the wrong revision. Your runbook should say what “abort” looks like: leave preview up, roll back the release, or freeze campaigns until metrics recover.
- Soft 404s returning 200 with empty states.
- Faceted URLs indexed and competing with canonical listings.
- FAQ schema on pages without visible FAQs.
QA checklist before you announce
- Happy path verified on mobile and desktop
- Failure path messaging reviewed
- Owners named for the first hour after launch
- Rollback or freeze path documented
Operating the change
After launch, watch the metrics that prove the change worked — not vanity charts. Pair quantitative signals with one qualitative check (support ticket themes, sales feedback). Schedule a follow-up within a week to remove temporary flags, raise DNS TTLs, or archive the experiment.
Tie SEO work to conversions, not rankings alone. Share a query-to-page map with ads and sales.
Treat SEO fundamentals as a repeatable playbook. The second time your team runs it should be faster because the checklist and owners already exist.
Write for humans first. Keyword stuffing still fails in obvious ways and trains bad editorial habits.
Internal links from strong pages help new URLs get discovered faster than hoping for crawl luck.
International hreflang belongs only on true locale variants with consistent reciprocity.
After IA changes, sample URL inspection beats assuming the sitemap alone fixed everything.
Product schema must match price and availability or rich results will drop — validate after catalog imports.
Keep a changelog of SEO-affecting publishes so you can correlate coverage swings with releases.