Technical SEO governs whether search engines can crawl, index, and understand your site. On-page SEO governs whether an individual page deserves to rank for a query. Technical problems must be fixed before launch because they cap everything else; on-page work continues indefinitely afterward.
The distinction sounds academic until a launch goes wrong. Then it becomes very concrete: a beautifully written page that search engines cannot crawl earns nothing at all.
The useful framing is sequence. Technical work sets a ceiling on everything else, so it belongs before launch. On-page work raises performance against that ceiling and never really finishes.
This guide separates the two cleanly: what each actually covers, the technical checklist that has to clear before launch, the on-page work that continues after, and how to read a symptom to know which layer is failing.
What is the difference between on-page and technical SEO?
Technical SEO is about access and comprehension: can a crawler reach this page, index it, and understand what it is? It covers crawlability, site architecture, canonical handling, structured data, redirects, and performance.
On-page SEO is about merit: does this page deserve to rank for this query? It covers content quality and depth, keyword and intent match, headings, metadata, internal links, and media handling.
The technical work that must happen before launch
- Crawlability and indexing. robots.txt, XML sitemap, and no stray noindex tags surviving from staging. This one has broken more launches than any other.
- Redirect map. Every old URL mapped to its new equivalent. Retrofitting this after launch means recovering losses rather than avoiding them.
- Canonicalization. One canonical URL per piece of content, so equity is not split across duplicates.
- HTTPS and performance. Valid certificate, sensible Core Web Vitals, no render-blocking obstacles to first paint.
- Analytics and Search Console. Configured before launch, or you will have no baseline to compare against.
The on-page work that continues after
Content depth, intent match, heading structure, metadata, and internal linking all improve iteratively once you can see real query data. Google's own guidance sets the bar for Largest Contentful Paint at 2.5 seconds or less, measured at the 75th percentile of page loads across mobile and desktop.
This is a feature rather than a compromise. Guessing intent before launch is unavoidable; correcting it against Search Console data afterward is far more accurate than any pre-launch keyword exercise.
Where the two overlap
Structured data, headings, and internal linking sit in both camps. They are implemented technically and they carry meaning, which is exactly why they get neglected by whichever specialist assumes the other owns them.
Assign them explicitly. Unowned overlap is the most common gap in a launch checklist.
How to tell which problem you have
When a page underperforms, the fix depends entirely on which layer is failing, and Search Console tells you where to look. Diagnose by symptom before you touch anything, because the wrong fix is just wasted effort against the wrong ceiling.
- Not indexed at all. A technical problem: crawlability, a stray noindex, or a canonical pointing elsewhere. On-page work is wasted until this is fixed.
- Indexed, no impressions. An intent or relevance problem. The page is understood but does not match what anyone searches. On-page.
- Impressions, few clicks. A title and meta description problem. You rank, but the snippet does not earn the click. On-page.
- Clicks, no conversion. Not an SEO problem at all. The page ranks and gets visited; the content or UX fails to convert.
A pre-launch order of operations
Confirm crawlability and indexing. Verify the redirect map against the full list of indexed URLs. Check canonicals and structured data. Validate performance on real devices. Confirm analytics is recording.
Then launch, and treat the first fortnight of Search Console data as the real audit. Pre-launch checks catch what you thought of; crawl data catches what you did not.
- ✓ Technical SEO caps what everything else can achieve, so it belongs before launch.
- ✓ On-page work improves iteratively and is more accurate once real query data exists.
- ✓ A stray staging noindex is the single most common launch-breaking mistake.
- ✓ Diagnose by symptom: not indexed is technical; indexed but no impressions is intent; impressions but no clicks is the snippet; clicks but no conversion is not SEO.
- ✓ Structured data, headings, and internal links sit in both camps and need an explicit owner.
FAQ
Which matters more, on-page or technical SEO?+
They are sequential rather than competing. Technical problems cap what on-page work can achieve, so they come first. Once the technical floor is solid, on-page determines actual performance.
My page is indexed but gets no traffic. Is that technical or on-page?+
On-page. If it is indexed, crawling and comprehension are working, so the gap is relevance and intent match, or a title and meta that do not earn the click. Technical SEO has done its job; the content layer has not.
What is the most common SEO mistake at launch?+
Shipping with a noindex tag left over from staging, or launching without a complete redirect map. Both are cheap to prevent and expensive to discover weeks later.
How soon after launch should you audit SEO?+
Watch Search Console daily for the first two weeks. Crawl errors and indexing problems surface fast, and fixing them before they are repeatedly crawled limits the damage.
Sources
- [1]A good Largest Contentful Paint is 2.5 seconds or less, measured at the 75th percentile of page loads. Google, Largest Contentful Paint (LCP), web.dev, accessed July 2026.