Crawlability and indexability are different questions
A crawler reaching a URL does not automatically mean the page will be indexed, and an indexed page does not automatically mean it will rank for a useful query. Start by separating access, canonicalization, rendering, indexation, and ranking into different diagnostic questions.
Check HTTP status codes, robots directives, canonical tags, sitemap inclusion, internal links, and Search Console evidence where access is available. A page marked noindex, canonicalized elsewhere, orphaned from the main site, or returning an inconsistent response can create a concrete technical problem. A page that is technically valid but offers little distinct value is a different problem.
02
JavaScript and page builders are not automatically bad
Modern search systems can process JavaScript, but rendering still adds complexity. Problems arise when important content, links, metadata, or navigation only appear after fragile client-side execution, fail under error conditions, or are difficult for users and crawlers to reach.
The correct test is not WordPress versus Next.js, or page builder versus custom code. Inspect the rendered output, response behaviour, page performance, accessibility, dependency weight, and whether important content remains available in a reliable form.
03
Internal links should reflect the information architecture
Important service and decision pages should be discoverable through normal navigation and contextual links. An orphan page with no meaningful incoming links is harder for users to find and gives search systems less context about how it relates to the rest of the site.
Avoid arbitrary rules such as every page must be exactly two clicks from the homepage. Large sites can require deeper structures. The useful principle is that important pages should have logical paths, descriptive anchor text, and a clear relationship to parent topics and related evidence.
04
Structured data must describe reality
JSON-LD can make page entities and relationships easier for machines to interpret, but it is not a shortcut around weak content or inaccurate business information. Structured data should match what a visitor can verify on the page and should not invent phone numbers, addresses, ratings, opening hours, services, or capabilities.
Use the most specific schema that accurately describes the visible content, connect stable entities with consistent @id values, and remove markup that represents features the site does not provide.
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://example.ca/#organization",
"name": "Example Business",
"url": "https://example.ca",
"email": "[email protected]"
}05
Performance is a user-experience problem before it is a score
Large images, third-party scripts, layout shifts, slow server responses, and heavy client-side work can make a site frustrating to use. Core Web Vitals provide useful field metrics for loading, responsiveness, and visual stability, but a perfect lab score is not a business outcome by itself.
Optimize the bottleneck you can measure. Reserve image dimensions, avoid unnecessary JavaScript, load optional third-party code deliberately, compress media appropriately, and test the finished experience on representative devices and networks.
06
Prioritize by decision value
A useful technical audit distinguishes critical failures from low-value cleanup. A broken canonical on a revenue page can deserve immediate attention. A minor warning on an irrelevant utility URL may not.
For every issue, document what was observed, which pages are affected, what evidence supports the diagnosis, what change is proposed, and how you will verify the result afterwards. That turns technical SEO from a warning list into an engineering process.
07
Redirects and URL changes during a redesign
A redesign can lose useful visibility when URLs change without a migration plan. Before launch, export the available URL history, including pages that received clicks or links, and decide where each one should go. A page with a clear replacement gets a permanent redirect to it; a page with no equivalent may be better returning a not-found status than redirecting to an unrelated homepage, which search engines may treat as a soft error.
Avoid redirect chains, where an old URL points to another old URL before reaching the live page. Each hop adds delay and risk. After launch, crawl the old URL list and confirm that every entry resolves in one step to a live, indexable page. Keep the map; it is the first thing to check if a page later disappears from results.
- Export URLs with clicks, impressions or backlinks.
- Map each one to its closest equivalent.
- Test the full list after deployment, not a sample.
- Keep the redirect map with the release notes.
08
Orphaned pages and weak internal links
A page that no other page links to is hard for crawlers to discover and hard for visitors to find. Orphans appear when navigation is simplified, campaigns end or a blog grows without structure. Compare the URLs in the sitemap with the URLs reachable by following links from the homepage; anything in the first list but not the second deserves a decision.
Internal links help visitors and crawlers understand page relationships. Different natural anchor phrases are not inherently a problem. The important question is whether a link takes the reader to the right answer: buying information belongs on a service page, while an explanation may belong in a guide. Choose the destination for its purpose, use descriptive wording and avoid forcing identical keyword anchors into every paragraph.
09
Triage one missing service page from response to render
Consider a hypothetical service URL that appears in the sitemap but receives no impressions. No impressions alone does not establish a technical fault: the page may be new, demand may be limited or the query may not match. Start by checking the actual published response. Does the URL return the intended page, redirect elsewhere or display a not-found template with a successful status? Record the response rather than relying on its appearance in a browser.
Check its indexing directive and canonical next. An accidental noindex or canonical pointing to an unrelated service is actionable evidence. A robots block is a different condition because it can prevent the crawler from seeing the page at all. Then inspect mobile rendered HTML: the service explanation and internal links should be available without a click that a crawler may never perform. Test a direct visit as well as navigation from the homepage.
Finally, use URL Inspection to distinguish a live accessibility test from Google's stored indexing information. A live test can show that a page is accessible now; it does not guarantee indexation. If the technical checks are sound, investigate content usefulness and query alignment rather than repeatedly requesting indexing. Keep the hypothesis open until the evidence supports a conclusion.
10
Turn a finding into an acceptance test
An issue record needs more than a screenshot of a red warning. Write the affected URL or template, observed behaviour, intended behaviour, proposed owner and verification method. For example, a canonical correction can be checked in the deployed response and rendered head, then revisited in Search Console after recrawling. Separate the completed code change from Google's later selection.
Keep unresolved dependencies visible: a booking provider may control its own domain, a CMS may restrict response headers, or historic exports may be unavailable. An explicit limitation is more useful than pretending the investigation covered every system. Once the high-confidence blockers are resolved, reassess the original question before starting another round of low-value fixes.
11
Duplicate and near-duplicate URLs
One page can be reachable at several addresses without anyone planning it: with and without www, over http and https, with and without a trailing slash, in upper and lower case, or with tracking parameters added. Visitors never notice, but search engines have to decide which version to keep, and links and signals can end up split between copies.
Pick one preferred form of every address and make the rest redirect to it with a permanent redirect. Then check that internal links, the sitemap and the canonical tag all use the same form. A canonical tag is a hint, not an instruction, so it works best when every other signal agrees with it. If your own links point to the non-preferred version, fix the links rather than relying on the redirect forever.
- Choose one protocol, one host name and one trailing-slash rule.
- Redirect every other form with a single permanent redirect.
- Use the preferred form in links, canonicals and the sitemap.
- Strip tracking parameters from internal links.
12
Titles, headings and metadata that describe the page
Each page needs a title that says what that page is about, written for the person who will read it in a list of results. Search engines may rewrite titles and descriptions, so treat them as a proposal. Duplicate titles across many pages are a common sign of a template that was never customized, and they make it harder for anyone to tell your pages apart.
Use one main heading per page, followed by subheadings that reflect the structure of the content. A heading is for the reader first. A meta description does not directly rank a page, but a clear one can help a person decide to click. For sets of similar pages, such as services or locations, write the title from the facts that differ between them, not from a pattern with one word swapped.
- One clear title per page, different from every other page.
- One main heading that matches the page's purpose.
- A description that is accurate and specific, not a list of keywords.
- Check the rendered page, since some platforms add or override tags.
13
Status codes and soft errors
Every address returns a status code, and the code should match reality. A working page returns 200. A page that has moved returns a permanent redirect. A page that no longer exists returns 404 or 410. A server fault returns a 5xx error. Trouble starts when a missing page shows a friendly 'not found' message but still returns 200, because a crawler may treat it as a real page with thin content.
Check the response itself rather than how the page looks in a browser. Your hosting platform, CMS or a developer can show headers for any URL. A useful 404 page includes a search box or links to the main sections, so visitors who land there can carry on. If a page is gone for good and nothing replaces it, a plain 404 is usually better than a redirect to the homepage.
- Test a deliberately wrong address and confirm it returns 404.
- List redirects and confirm none point to another redirect.
- Watch for 5xx errors in hosting logs, especially after releases.
- Review the Pages report in Search Console for soft 404 warnings.
This guide explains a method. Service scope, access, responsibilities and fees are agreed for the actual project; rankings, AI citations and conversion gains are not guaranteed.
technical SEO services