Technical SEO makes sure search engines can crawl, render and index your pages. On-page SEO makes each page relevant and useful for the keyword it targets. Technical SEO lays the foundation, and on-page SEO decides what Google finds once it gets in.
Both happen on your own website, which is why the line blurs. Page speed, structured data, internal links and mobile layout sit in both camps. This guide shows where that line sits, who owns each task, and which to start with based on the symptom you see.
What is the difference between technical SEO and on-page SEO?
The difference between technical SEO and on-page SEO is the layer you optimize. On-page SEO focuses on the content and on-page elements of a single page: the title tag, headings, copy, images and the keyword the page targets. Technical SEO focuses on the infrastructure under every page: crawling, indexing, rendering, site speed, redirects, canonicals and the server. Both are parts of search engine optimization, and both feed the same goal: search visibility for pages that make you money.
Both decide how your page appears and how well it ranks on the search engine results page. If you want the full picture of what shows up there and why, our guide to SERP meaning covers every result type in 2026.
A simple test helps. If a writer can fix the problem in the CMS editor, it is on-page optimization. If the fix needs a developer, a template change or server access, it is a technical fix.
Technical SEO vs on-page SEO vs off-page SEO at a glance
Most guides compare 2 disciplines. In practice you are always juggling 3, because off-page SEO decides how much authority your site brings to the fight.
| On-page SEO | Technical SEO | Off-page SEO | |
|---|---|---|---|
| Core question | Does this page match the search and help the visitor? | Can search engines reach, render and index the page? | Do other sites trust and mention this site? |
| Typical tasks | Keyword targeting, title tags, meta description, headings, copy, internal links, image alt text | Crawl access, indexing directives, canonicals, redirects, site speed, Core Web Vitals, rendering, sitemaps | Backlinks, digital PR, brand mentions, reviews |
| Scope | 1 page at a time | Templates and the whole site | Your domain and brand |
| Usual owner | SEO strategist and writer | Developer with an SEO specialist | SEO or PR specialist |
| Tools | Search Console queries, NeuronWriter, the SERP itself | Search Console indexing reports, crawlers, PageSpeed Insights | Backlink tools, PR databases |
| How fast it shows | Weeks after recrawl | Fast for blockers, slow for speed gains | Months |
Off-page SEO is the layer you control least, and the on-page vs off-page SEO split matters less than getting all 3 to work together. Our content SEO vs technical SEO guide goes deeper on the content side and how to measure each type of work.
Where on-page and technical SEO overlap
On-page and technical SEO overlap in 4 places. Each overlap has an on-page decision and a technical implementation, and both halves need to be right.
Page speed. Site speed is technical: server response, caching, image compression, script loading. But on-page choices add weight. A writer who embeds 6 videos and a 4MB hero image makes a page slow on a fast server, and that hurts user experience before it hurts ranking. Google measures real-world page experience with Core Web Vitals: Largest Contentful Paint (loading, good under 2.5 seconds), Interaction to Next Paint (responsiveness, good under 200 milliseconds) and Cumulative Layout Shift (visual stability, good under 0.1), per Google's Core Web Vitals documentation. INP replaced First Input Delay as a Core Web Vital on March 12, 2024. Many SEO guides still list FID, so check the date on any advice you follow.
Structured data. Deciding what to mark up is on-page: product price, reviews, FAQs that exist on the page. Adding the JSON-LD to templates and keeping it valid is technical. Structured data has to match the visible text, or it does more harm than good.
Internal links. Choosing which pages link to which, and with what anchor text, is on-page and strategic. Making those links crawlable HTML links in menus, filters and pagination is technical. A link Google cannot follow passes nothing.
Mobile. Google uses the mobile version of a page, crawled with its smartphone agent, for indexing and ranking, per its mobile-first indexing guidance. Responsive templates are technical. Content that only appears on desktop, or tap targets packed too close, are on-page fixes.
What technical SEO covers
Technical SEO covers everything that decides whether search engines can crawl, render and index your pages efficiently. A technical audit usually checks these areas:
- Crawl access: robots.txt rules, firewall settings, crawlable links, pagination.
- Indexing: noindex tags, canonical tags, duplicate URLs from filters and parameters.
- Rendering: content that loads through JavaScript and whether Google sees it.
- Speed and Core Web Vitals: server response time, page weight, layout shifts.
- Site structure: XML sitemaps, redirects, status codes, HTTPS.
An Australian ecommerce store on Magento 2 looked fast to every person who checked it. Cached pages loaded in 0.09 to 0.18 seconds, so the first instinct was that speed was fine. A crawl of 37,898 URLs told a different story. Uncached pages took 1.8 to 3.0 seconds to first byte, and 54% of URLs took 3 seconds or longer. Worse, a firewall rule returned a 403 error to Googlebot on a category that had ranked #2. Category pages carried 490 to 757KB of HTML and over 4,000 DOM nodes, with the copy below the product grid. Blocked pagination meant Google could reach 48 of 344 products. The fixes went to the developer. The lesson: a technical problem can hide behind a page that looks perfect to you.
What on-page SEO covers
On-page SEO covers the content and signals on each page that help search engines and visitors understand what the page is about. Content optimization usually covers these areas:
- Keyword targeting: 1 primary keyword and intent per URL, chosen through keyword research.
- Title tag and meta description: the headline and summary shown in search results.
- Headings and copy: a clear H1, logical subheadings, and content that answers the search.
- Page type: a collection page, product page, service page or article, matched to what ranks.
- Internal links and anchor text: links from related pages pointing at the page that should rank.
- Images: descriptive file names and alt text.
Our guide to what on-page SEO is covers each element in more detail.
Which should you fix first? Start from the symptom
Fix whichever problem stops the page from doing its job right now. When the page cannot be indexed, start with technical SEO, because no amount of content quality helps a page the search engine cannot see. Once the page is indexed, on-page work usually moves search engine rankings faster than more technical fixes. Use the symptom to pick the starting point.
| If you see this | Start with | First check |
|---|---|---|
| Page not on Google at all | Technical | URL Inspection in Search Console: indexed, blocked, or noindex |
| "Crawled, currently not indexed" on many pages | Both | Thin or duplicate content first, then internal links to those pages |
| Indexed but ranks nowhere for its keyword | On-page | Does the page type match what ranks on page 1 |
| Ranks on page 2 (positions 11 to 20) | On-page | Title tag, missing subtopics, internal links from related pages |
| Rankings dropped right after a redesign or migration | Technical | Redirects, canonicals, robots.txt, lost internal links |
| Impressions but very few clicks | On-page | Title tag and meta description against the SERP |
| Good rankings on desktop, weak on mobile | Technical | Mobile rendering and Core Web Vitals field data |
| Wrong page ranks for the keyword | On-page | Keyword cannibalization and internal link anchors |
| Strong pages, stronger competitors | Off-page | Referring domains gap against the top 3 results |
The page 2 row is often the fastest win. Our guide on how to get to page 1 on Google walks through that exact play.
Who owns each task: writer, developer or SEO
Ownership is where most SEO efforts stall. A task with no clear owner sits in a backlog for months, so assign every task an owner before the work starts.
| Task | Writer or content team | Developer | SEO specialist |
|---|---|---|---|
| Keyword research and page mapping | Supports | Owns | |
| Title tags, headings, copy | Owns | Reviews | |
| Template title and meta rules | Builds | Specifies | |
| Internal linking plan | Adds links in copy | Fixes menus and pagination | Owns the plan |
| Structured data | Keeps content accurate | Implements JSON-LD | Specifies and validates |
| Site speed and Core Web Vitals | Keeps media light | Owns | Monitors |
| Indexing, canonicals, redirects | Implements | Owns the rules |
The SEO specialist connects the 2 sides and sets the content strategy. On a small team, that may be you: your job is to write clear tickets for the developer and clear briefs for the writer.
How AI search changes the split
AI search adds weight to both technical and on-page SEO. Google states that AI Overviews and AI Mode need no special optimization. A page must be indexed and eligible for a snippet to appear as a supporting link, per its AI features documentation. That makes technical SEO the entry ticket: an unindexed page cannot be cited by any search engine feature.
On-page structure then decides whether a passage is easy to lift. A section that opens with a direct answer and names its subject reads well on its own. That structure improves the odds of being retrieved and cited by AI assistants. It guarantees nothing.
Get both layers working together
A well-rounded SEO strategy runs both layers at once. Pick your most important page, find its symptom in the table above, and fix that first. If you want a team to run the on-page work and write clear technical tickets for your developer, see our on-page SEO services.