Technical SEO, from crawl to index.

• Choose technical SEO when pages are missing, duplicated or slow to index.

  If Search Console shows real pages outside the index, or several URLs competing to represent one page, the cause is technical and content work will not reach it.

• Choose on-page SEO when pages are indexed but match the wrong searches.

  Indexed pages that earn impressions for queries they answer badly need their intent, titles and headings fixed rather than their directives.

• Choose a rebuild when the platform cannot render content on the server.

  Some rendering problems are configuration and some are the framework itself. When the front end cannot be server-rendered, the fix is website redesign and modernization.

A crawler discovers a URL through links or a sitemap, requests it if robots.txt allows, renders the returned HTML and any JavaScript, then decides whether to index the page and which URL is canonical. Each stage can fail independently, so a missing page is diagnosed stage by stage rather than guessed at.

In Google Search, rendering is a separate step that can happen after the initial crawl, which is why content present only after JavaScript runs may be indexed late or incompletely. Server rendering or static generation removes that dependency by putting the words, links and structured data in the first response.

• Discovery: internal links, sitemaps and links from other sites.
• Crawling: permitted by robots.txt and served with a 200 status.
• Rendering: the HTML and scripts the page needs to show its content.
• Canonical selection: one URL chosen to represent a set of duplicates.
• Indexing: the page stored and eligible to be shown in results.

Canonicalization tells search engines which URL represents a page when several URLs show the same or very similar content. Without it, the engine picks a canonical itself, and ranking signals can be divided across parameter, protocol, trailing-slash and tracking variants of what is really one page.

The canonical tag is one signal among several. In Google Search, redirects are the strongest of them, canonical tags are strong and sitemap inclusion is weak, and each one indicates a preference. The reliable result comes from making them agree: internal links point at the canonical URL, redirects end on it, the sitemap lists it, and the tag confirms it.

An XML sitemap should list the canonical URLs you want indexed, each returning a 200 status, and nothing else. Redirects, noindexed pages, duplicates and error pages do not belong in it. A sitemap helps search engines discover pages on large or poorly linked sites, but it does not guarantee that any of them are indexed.

The sitemaps protocol allows up to 50,000 URLs or 50 MB uncompressed in one file, with a sitemap index file joining several files beyond that. Google Search ignores the priority and change frequency fields, and uses the last modified date only when that date is consistently accurate, so a date that changes on every deployment is worse than no date.

• Only canonical URLs that return a 200 status.
• No redirected, noindexed or robots-blocked URLs.
• A last modified date only where it reflects a real content change.
• Separate files joined by a sitemap index beyond the protocol limits.
• The sitemap declared in robots.txt and submitted to Google and Bing.

Structured data is worth adding where it accurately describes content visible on the page and matches a type the engine supports, such as Organization, BreadcrumbList or Product. It becomes a risk when it describes anything the page does not show, including reviews, ratings, prices or authors, which is a structured data policy violation.

Markup can make a page eligible for some enhanced search results; it does not guarantee them, and misleading markup can lead to a manual action. We generate structured data from the same data that renders the page, so the markup and the visible content cannot drift apart when either one changes.

• Technical SEO
• Crawlability
• Indexing
• Canonicalization
• XML sitemap
• Robots.txt optimization
• Structured data
• Schema markup
• Image SEO
• Search Console setup

Every page passes through the same four stages before it can appear anywhere in search, and each stage has its own controls. A problem at an early stage cannot be fixed by work on a later one.

• Every page that should compete can

  Removing crawl and index blockers is the precondition for everything else. Content and links cannot help a page that a search engine never stores.

• Signals point at one URL

  Canonicals, redirects, internal links and the sitemap agree with each other, so the authority a page earns is not divided across its duplicates.

• Machines read what people read

  Server-rendered content and accurate structured data mean search engines and AI systems receive the same information a visitor sees.

• Problems are found early

  Monitoring in Search Console and Bing Webmaster Tools catches a broken release before its effect shows up in traffic reports.

• A site with a large not-indexed report

  Hundreds of URLs sit outside the index. The work separates the duplicates and low-value pages that should stay out from the real pages being blocked.

• A JavaScript front end that indexes slowly

  A client-rendered application needs rendering moved to the server or the build, which is an engineering change rather than a setting.

• A store drowning in parameter URLs

  Filters and sort orders generate far more URLs than products. Canonical rules and crawl controls return attention to the category and product pages.

• Search Console and Bing Webmaster Tools are the ground truth for coverage. Third-party crawlers are used to find causes, not to report scores.
• robots.txt manages crawling and is never used to hide a page from the index, because a blocked URL cannot show its noindex directive.
• Canonical tags, redirects, internal links and sitemap entries are made to agree, since conflicting signals leave the choice to the engine.
• Sitemaps list only canonical, indexable URLs that return a 200 status, with a last modified date only where it reflects a real content change.
• Structured data is generated from the same data that renders the page and describes only what a visitor can see.
• Images carry descriptive alternative text and explicit dimensions, in modern formats such as WebP, inside real img elements rather than CSS backgrounds.
• Core Web Vitals diagnosis and speed work belong to performance and security. Technical SEO flags them and hands them over.