When is an SEO problem technical? When a crawler cannot reach the URL, cannot tell which URL should be kept, or cannot see the content in the HTML it stores. If the fetch is clean and the page still describes the wrong job, the problem is the words. Technical SEO is the unglamorous layer. A Field Guide to Technical SEO is the longer account. This article is the split, so a missing paragraph does not get filed as a rebuild.
Takeaways
- Technical means fetch, index, canonical, redirect, or a template that hides the content.
- Words mean the fetch is fine and the page says the wrong thing.
- Every finding needs the URL that shows it.
- A faster host does not repair a heading missing from the HTML.
- A new site can carry the same template mistake.
A Fetch Problem
Open the URL the way a crawler would, not only the way a browser paints it. If the heading a visitor sees is absent from the HTML that comes back, the template is hiding the content. That is technical. The SEO Starter Guide starts from the idea that search has to be able to find and understand the page. A page that only exists after a script the crawler does not run has not cleared that bar.
Redirect loops, blocked folders, and a canonical that points every URL at the homepage are the same family. The visitor may still muddle through. The index will not. Name the URL that shows the pattern. A thousand copies of one template bug are one task, not a thousand tasks.
A slow host is not automatically this problem. Speed matters when it blocks the fetch or hides the content. It is not a substitute for reading the HTML.
Name the one thing that is stuck before you ask for a new building.
A Words Problem
If the fetched page contains the heading, and the heading describes a different job than the query you wanted, you are done with the crawl. On-Page SEO is the next owner. A Practical Guide to On-Page SEO says to write the query down before the title changes.
A thin paragraph is not a crawl error. A missing service you do not actually sell is not a technical debt. Adding the words to a URL that is excluded from the index wastes the writing. Confirm the fetch first, then write. Do not reverse it, and do not do both under one vague ticket called "SEO."
Two URLs with the same clean fetch, competing for one query, are also a words problem. The canonical might be a technical tool you use after you pick a winner. The decision about which page should exist is not a server setting.
How to Tell Them Apart
Use one question: what would a developer change, and what would a writer change?
- Fetch the URL and save the HTML.
- If the important words are missing from that HTML, write a template task.
- If the words are there and they are the wrong words, write a content task.
- If you cannot say which sentence it is, you do not have a finding yet.
A tool that mixes both into one export is not wrong to run. It is wrong to hand to a single person as if the rows were the same kind of work. Split the export before the meeting, or the meeting will argue about a score instead of a URL.
What to Hand a Developer
A developer needs the URL, what the fetch shows, and the change in the template. "Make it SEO friendly" is not a task. "This product URL canonicals to the homepage; here is the HTML; stop doing that" is a task.
| What you see | Call it | Hand it to |
|---|---|---|
| Heading missing from the fetched HTML | Technical | A developer, with the URL |
| Redirect loop or blocked folder | Technical | A developer, with the URL |
| Fetch is clean, title disagrees with the page | Words | A writer, after the query is chosen |
| Two clean URLs want the same query | Words first | Whoever picks the winner, then a canonical if needed |
Technical SEO asks for fixes a developer can ship, written as tasks rather than a slide. If the note cannot be shipped, it is not finished, whether or not it sounded technical in the report.
A Short Test Before You Rewrite the Page
Before you change a word, ask whether the words are even what gets fetched. Open the URL the way a crawler would have to meet it. If the address redirects somewhere else, the page you are editing may not be the page that gets indexed. If the text you care about appears only after a click that a crawler does not make, a better paragraph will not be read. If two addresses show the same page and neither one is named as the preferred URL, you are about to polish a duplicate. Those are technical facts. They are visible before any rewrite.
Do the test in this order, and write one line for each:
- What is the address a person is sent to, after redirects?
- Does the fetched page contain the sentence you think is the page?
- Is there a second address that also claims this content?
- Can you see the page in Search Console as indexed, excluded, or unknown?
If the first three lines are messy, stop the copy edit. The job is a fetch problem, and it belongs with Technical SEO. Hand the developer the URL, the line that failed, and the change you need: one address, the sentence present in the fetched HTML, a single preferred URL. A Field Guide to Technical SEO is the longer version of that handoff. You do not need a new site to answer those four lines.
If the four lines are clean and the title still describes a different job than the first screen, you have a words problem. Rewrite the title and the heading. Do not open a ticket that says "SEO the page." A developer cannot ship that. They can ship a canonical, a redirect, or a template change that stops hiding the text.
A score from a plugin does not replace the four lines. A slow score can sit on a page that fetches perfectly. A high score can sit on a page that redirects in a circle. Use the plugin if you already have it. Believe the URL test when they disagree.
When you are unsure, write both notes and do the fetch note first. A beautiful heading on a URL that never gets indexed is a private document. SEO Audits is the right container when the site has many of these, and you need them in an order. One URL is enough to learn the difference. You do not have to crawl the whole domain to stop editing the wrong layer.
Questions
Is a Missing Meta Description Technical?
Only as a field in a template. The sentence inside it is a words decision. Do not open a crawl project because one description is empty. Decide what the URL is for, then fill the field.
Do I Need a New Site?
Usually not. Most of these problems sit in a template, a redirect, a canonical, or a rule. A new site can carry the same mistake. Name the URL before you name a rebuild.
Can a Plugin Score Tell Me Which It Is?
No. A score does not say whether the heading is in the HTML. Fetch the URL. The score can stay in the drawer.
Who Owns the Canonical?
A developer implements it. Someone who understands the pages chooses which URL should win. A canonical without that choice just hides the disagreement.
Conclusion
An SEO problem is technical when the crawler cannot fetch, keep, or read the URL. It is a words problem when the fetch is clean and the page still says the wrong thing. Split the list, put the URL on every line, and hand each line to the person who can change it. A rebuild is not the default.
If you want crawl issues written as tasks a developer can ship, Speak With Us.
