Technical SEO examines whether a page can be discovered, requested, interpreted and presented consistently with its purpose. It cannot establish that the page deserves a particular ranking, and it cannot rescue an explanation that fails to answer its reader's question. A useful audit connects the inspectable technical conditions with the document that people actually receive.
Use this checklist for a representative public page, then repeat it across the important templates on the site. A service page, an article and a product category may use different metadata components and routing rules. Testing the homepage alone does not prove that those other templates work. Choose the sample deliberately and keep untested areas visible in the final report.
Establish the document you are inspecting
Request the intended URL directly and note the final response after redirects. Check that the content belongs to the path you expected. A successful response containing a generic error message is not equivalent to a functioning detail page. Record the requested URL, final URL, response status and a brief description of the visible content before interpreting metadata.
Run the focused SEO tool when you want SEO-related results without mixing in unrelated security or delivery findings. Use the response inspection guide if the request itself needs investigation. A technically meaningful SEO review begins with the page that was actually fetched, not the page name entered into a form.
Review discovery routes
Follow links from relevant categories, navigation and related content. Important pages should have understandable paths for people to reach them. A sitemap can offer another discovery source, but it does not excuse a confusing internal architecture. Compare the routes you expect visitors to use with the links the website actually publishes.
For a fictional service site, a new repair page might appear in a sitemap while remaining absent from the services navigation. The page is published, but its relationship with the site's other information is weak. Investigate the publishing process and navigation ownership before adding unrelated links across every footer. The crawl-coverage article explains how a discovered graph differs from a complete publishing inventory.
Reconcile indexing and canonical decisions
Inspect the page's indexing directives and preferred-URL declaration together. Ask whether the page is intended for public search discovery and whether duplicate variants should remain separately accessible. Avoid making every page indexable simply because a checker notices a restriction. Temporary previews, internal search results and useful public articles may require different decisions.
Use the indexability explanation for a decision-oriented review and the canonical guide for duplicate identity. If a canonical target is unavailable or clearly unrelated, investigate the template producing it. If robots restrictions prevent a relevant crawler from seeing a response, review the policy before assuming the page's other directives have been observed by that crawler.
Compare titles, descriptions and visible headings
Read the browser title, description, main heading and introduction as a set. They should describe the same document without all repeating an identical promotional sentence. A reader should recognize the page's subject and understand what information is available. Specific metadata is particularly important when several related pages would otherwise be difficult to distinguish.
The metadata writing article provides an editing process, while the heading article addresses the document outline. A length warning is a reason to review wording, not permission to remove important distinctions or add meaningless phrases. Keep the title accurate even when the relevant topic cannot be summarized by a rigid formula.
Assess usefulness without padding the page
Read the explanation and list the questions it actually answers. Does it define unfamiliar terms, show an applicable example, explain important limitations and tell the reader how to proceed? A page can be long while repeating the same claim. Another may be concise because its purpose is narrow. Editorial completeness should be judged against the task, even when a project also sets a minimum writing length.
For an illustrative diagnostic article, practical depth might include the observation to collect, how to interpret conflicting evidence, where a change belongs and how to verify it. Adding an unrelated history section solely to increase the word count would not improve that article. Compare related pages for duplicated intent and make each one's particular question visible in its title and structure.
Inspect images and machine-readable context
Review important images for their actual informational role and alternatives. An empty alternative can be deliberate for decoration; an informative diagram may need a substantial explanation in the surrounding text. The image-alt guide shows why attribute presence and meaningful equivalence are different review tasks.
If the page includes structured data, compare it with the visible document. A markup block should not describe a service, review or offer that the page does not actually contain. A public scanner can inspect some syntax and signals, but it should not be used to promise eligibility for a search presentation or inclusion in an AI answer. Keep those outcomes separate from the facts available in the page response.
Verify source output and browser behavior
Open the page through ordinary internal navigation as well as a direct visit. Confirm the correct article or product appears and that metadata does not remain from the previous screen. Where JavaScript changes the document, distinguish initial-response evidence from the rendered result. That distinction matters when explaining what a particular tool could inspect.
Turn confirmed issues into a prioritized work list with exact URLs and source ownership. After deployment, retest the original examples and a second page using the affected template. Use scan comparison to retain an understandable before-and-after record. The strongest technical SEO checklist is one that produces verifiable changes while remaining honest about what public evidence cannot establish.
Compare technical checks with editorial decisions
| Approach | Evidence | Useful for |
|---|---|---|
| SEO audit | Inspectable SEO and document signals | Finding relevant technical observations |
| Keyword comparison | Phrase placement and extracted competitor content | Exploring an editorial question |
| Human review | Accuracy, usefulness and intent | Deciding whether the explanation serves readers |
Using CrawlNFix for this task
Use CrawlNFix's free SEO audit as the technical observation stage, not as a substitute for writing and judgment. No paid plan or login is needed to review the public page. An internet connection is necessary to fetch its current output. Saved HTML/text can be compared locally in the keyword tool, which is useful when you want to examine wording offline without pretending it is a live crawl.
Record an answer for each checklist decision
| Check | Evidence to keep | Decision and verification |
|---|---|---|
| Response | Requested URL, final URL and returned status | Confirm that the intended document is delivered; retest the original entry URL after changing a rule |
| Indexing | Meta robots, response directives and intended page purpose | Correct only unintended restrictions; compare the deployed values with your indexing decision |
| Canonical | Declared URL and the target response | Reconcile duplicate variants and inspect related template pages after a change |
| Title and headings | Source title and visible heading outline | Describe this page specifically; verify the resulting source and rendered outline |
| Discovery | A real internal link and any sitemap entry | Confirm that the source publishes the route, then repeat a bounded crawl with coverage recorded |
A checklist is useful when each row can lead to a reproducible follow-up. For example, if an article inherits the homepage title, keep both source values and identify the shared template. Correct the article's metadata binding, then inspect that article and a second article using the same layout. Merely adding the words “SEO audit” does not address the underlying template mistake. Use the canonical fix guide for the operational steps and SEO checker for the supported page evidence.