Technical SEO Foundations: What to Fix Before Content

Content cannot rank if Google cannot crawl it, render it, or decide which URL is the real one. Publishing more pages on a broken foundation just creates more URLs that sit in “Crawled — currently not indexed.” Fix crawl, speed, and structure first. Then content has a chance.

This page is the install checklist. The technical SEO audit is how we prioritize a live site.

Crawlability

Google has to find the page, fetch it, and keep it in the index. If any of those fail, the rest of SEO is theater.

Robots.txt

Allow service pages, blog posts, and CSS/JS. Block admin, search-result URLs, and thank-you pages. Add a Sitemap: line so crawlers do not have to guess.

Common mistakes:

• A leftover Disallow: / from staging
• A rule that blocks /blog/ because someone wanted to hide drafts
• Blocking CSS/JS so Google cannot render the page you think you shipped

Check yoursite.com/robots.txt and the robots tester in Search Console before you write another post.

Sitemap

The sitemap is a priority list, not a dump of every URL your CMS ever created. Include:

• Canonical versions of important pages only
• Current lastmod dates
• No redirects, 404s, or noindexed URLs

Submit it in Search Console. If submitted count and indexed count diverge by a lot, you have crawl or quality issues — not a “need more posts” problem yet.

Indexation and crawl budget

Search Console → Pages is the truth. Look for accidental noindex on templates, tag archives competing with real pages, and parameter URLs eating crawl budget. Thin or duplicate URLs get crawled and skipped. That is an index-coverage problem, not a content-calendar problem.

On large catalogs, crawl budget is finite. Do not spend it on sort/filter clones. Canonicals, parameter handling, and a tight sitemap keep Google on the URLs that can take an RFQ. Forzabuilt’s 200+ SKU Astro rebuild needed that discipline plus layered redirects; post-remediation technical SEO health hit 99%.

When: fix crawl and indexation before a content sprint or a redesign. After: check the Pages report weekly until the index looks like the site you meant to ship.

Titles and meta descriptions

One unique title and one unique meta per URL. They are the SERP snippet, not a place to dump every keyword.

• Title: 50–58 characters. State the job or the query. Do not append | Brand if that pushes the title past 60.
• Meta: 140–155 characters. Answer first, then the proof or the CTA. Do not write “Learn more about…” filler.

If two service pages share a title, they will compete. If the meta is 80 characters, you donated the snippet to Google’s rewrite.

Speed

Speed is a ranking factor and a conversion factor. Google uses Core Web Vitals as part of page experience. Buyers bounce before the hero finishes loading.

Metric	What it measures	Target
LCP	Largest visible content	Under 2.5s
INP	Time to respond to a click	Under 200ms
CLS	Unexpected layout shift	Under 0.1

Field data in PageSpeed Insights (Chrome UX Report) beats a one-off Lighthouse score. Lab scores are for debugging. Field data is what Google sees at scale. Forzabuilt’s media-heavy catalog held a 99% Lighthouse desktop score after the rebuild — the template bar, not a brochure theme.

TTFB should stay under 600ms. A heavy theme on uncached shared hosting will lose to a simpler page that answers in 200ms.

Images

Images are usually the LCP element. Serve WebP (or AVIF) at the displayed size, not a 4000px original. Width and height attributes to stop CLS. Lazy-load below the fold only — never the hero. Descriptive filenames and alt that name the part or process, not “image1.”

When: if mobile LCP is over 2.5s, stop publishing and fix the template. One slow template multiplies across every new URL.

Structure

Canonicals

Every indexable page should have one canonical, and it should match the URL you want to rank — including https, www, and trailing slash. Wrong canonicals split signals or point a service page at the homepage. Audit that before you add more near-duplicate service variants.

Schema

Start with Organization (who you are) and BreadcrumbList (where the page sits). Add Service on service pages and Article on posts. Markup must match visible content. Invalid or stuffed schema does not create rich results; it fails validation.

Headers

One H1 that states the topic. H2s for sections. H3s under those H2s. Do not skip levels to style the page — CSS handles size. Headers are the outline Google and buyers both scan.

Accessibility that also helps crawl

Accessible pages are easier to render and easier to quote. Real headings (not styled divs), text alternatives on meaningful images, form labels, and keyboard-usable nav and CTAs. If the RFQ cannot be completed with a keyboard or a screen reader, you lose buyers and you ship a brittle DOM.

Sequence

1. Unblock crawl and confirm key URLs are indexable
2. Get LCP, INP, and CLS into range on templates
3. Fix titles, metas, canonicals, schema, and heading outlines
4. Then write and ship content

Do it in that order. Content on a crawlable, fast, unambiguous site compounds. Content on a broken one waits in the queue.

We fix technical foundations first. Start a search audit or start a project.