The two options
The work of making pages reachable, renderable and indexable — crawling, JavaScript execution, status codes, canonicals and site speed.
- Indexed page count is far below your published page count
- Content is injected by JavaScript and may not render for crawlers
- You have migrated, replatformed or changed URL structure recently
- Search Console reports crawl anomalies, soft 404s or redirect chains
The work of making an indexed page the best answer for its query — intent match, depth, structure, internal links and titles.
- Pages index cleanly but sit on page two for their target terms
- You rank for the term but the page answers a different intent
- Competitors cover sub-questions your page never mentions
- Titles and headings describe the company rather than the query
How they differ
| Technical SEO | On-page SEO | |
|---|---|---|
| What it fixes | Whether the page can be seen | Whether the page deserves to win |
| Failure symptom | Pages missing from the index entirely | Pages indexed but stuck below the fold |
| Who does the work | Engineering, with SEO specifying | Content and SEO, engineering rarely needed |
| Time to signal | Days to weeks once deployed | Four to twelve weeks after recrawl |
| Ceiling | Removes a cap; rarely wins a term on its own | Wins terms, but only on pages engines can read |
What actually decides it
The diagnosis is cheaper than either fix. Compare your published URL count against indexed URLs in Search Console. A large gap points at technical work. A small gap with weak rankings points at on-page. That single comparison resolves most of the argument in an afternoon, and it is the first thing an audit looks at.
The mistake worth naming is buying a content programme while a rendering fault is live. Content commissioned against a broken render is money spent on pages engines cannot read, and the deficit compounds because you keep publishing into it. That is why almost every engagement here opens with a technical pass even when the client is convinced content is the problem.
The reverse mistake is rarer but real: endless technical polish on a site that already indexes perfectly. Core Web Vitals moving from good to slightly better does not outrank a competitor with genuinely deeper coverage. Once the gate is open, the constraint has moved, and continuing to work the gate is comfortable rather than useful.
Questions
How do I know which one I need without an audit?
Compare published URLs against indexed URLs in Search Console. A large gap is technical. If nearly everything is indexed and rankings are still weak, the constraint is on-page. That check takes an afternoon and settles most cases.
Can we do both at once?
Yes, and larger teams usually do because they are different people. The sequencing only matters when you have to choose. If you are commissioning content, at least confirm the pages render for crawlers before you brief the work.
Does technical SEO matter for AI search too?
More than it did. Generative engines retrieve from indexes and their crawlers are less tolerant of JavaScript than Googlebot. A page that renders badly is invisible to assistants even when it ranks acceptably in classic search.
Which gives faster results?
Technical, usually. Fixes deploy and take effect on recrawl, often inside a month. On-page changes need recrawl plus reassessment against competitors, which typically means four to twelve weeks before the trend is readable.
Related services
- Technical SEO Audit — SEO
- On-Page SEO — SEO
- Core Web Vitals — SEO
- Keyword Research — SEO
Still not sure?
Thirty minutes with a senior strategist. We pull your live visibility while we talk and tell you which of these two is actually binding for you — including when the answer is neither. Book a discovery call →