Comparisons
Technical SEO vs On-Page SEO: Where the Boundary Is
The distinction is not really about the work — it is about what fails. Technical problems stop a page existing in search. On-page problems stop it competing.
Run a fresh DomainLens audit and use the report as your priority list.
A more useful definition than the usual one
The textbook split says technical SEO is about crawling and indexing while on-page SEO is about content and markup. That is roughly true and breaks down constantly — a canonical tag is markup on a page and is entirely a technical concern.
A better test: technical problems prevent a page from being eligible; on-page problems prevent it from winning. A blocked page cannot rank at any quality. A perfectly crawlable page with the wrong content ranks poorly no matter how clean the infrastructure.
| Concern | Category | Failure mode |
|---|---|---|
| Status codes, redirects | Technical | Page is not reachable |
| robots.txt, noindex | Technical | Page is excluded |
| Rendering, crawlable links | Technical | Content is not seen |
| Canonical, hreflang | Technical | Wrong version indexed |
| Core Web Vitals | Both | Experience, and a ranking input |
| Title, headings, copy | On-page | Ranks poorly |
| Intent match | On-page | Ranks for nothing useful |
| Internal links | Both | Discovery and authority |
Which to fix first
Technical, always — but only the blocking parts. A page returning 500, carrying a stray noindex, or serving an empty shell to crawlers cannot benefit from any content work, so those come first regardless of effort.
Beyond the blocking set, the ordering inverts. Once pages are reachable and indexable, on-page work almost always returns more than further technical refinement. Shaving 100ms off TTFB on a page whose content does not match the query is not the constraint.
A working order
Steps one and two are usually days of work. Step three onwards is ongoing. Most sites treat that ratio in reverse. See how to prioritise SEO fixes for ranking within each category and how to improve Google rankings for the diagnostic sequence.
- 1Fix anything blocking indexation — status codes, robots directives, canonical conflicts, rendering failures.
- 2Confirm the important pages are actually indexed, rather than assuming the fix worked.
- 3Check that each page targets a question with real demand and matches its format.
- 4Improve the content of pages already ranking on page two, where small gains convert to visible movement.
- 5Return to technical refinement — performance, structured data, internal link distribution.
- 6Repeat, starting from what the data now shows rather than from the checklist.
Where they genuinely overlap
The overlap is a good argument for not treating the categories as separate workstreams. They are labels for kinds of failure, not for teams.
- Core Web Vitals — technical to fix, and a ranking input like on-page factors.
- Internal linking — a crawl-discovery mechanism and an editorial decision about relevance.
- Structured data — markup, but only valid when it matches the content it describes.
- Canonical tags — a technical directive resolving what is fundamentally a content duplication question.
How DomainLens contributes
DomainLens covers the technical half mechanically — status, indexability, canonical, rendering, performance, markup — which is exactly the half a tool can settle. It deliberately does not grade whether your content answers the question, because that is the on-page half and no tool assesses it honestly. See the technical SEO checklist and the on-page checklist .
- What is the difference between technical and on-page SEO?
- Technical problems stop a page being eligible to rank at all. On-page problems stop an eligible page from competing. The work overlaps; the failure modes do not.
- Which should I fix first?
- Anything blocking indexation, immediately. After that, on-page work usually returns more than further technical refinement.
- Are Core Web Vitals technical or on-page?
- Both. They are fixed through technical work and act as a ranking input the way on-page factors do.
- Can good content overcome technical problems?
- Not the blocking ones. A page that cannot be crawled or is excluded by a directive does not rank at any quality of content.