Technical SEO Checklist for Titles, Canonicals, and Indexing

Technical SEO should remove conflicting signals

A page can have a title about building websites, an H1 naming a product, a canonical URL pointing to the homepage, a noindex directive, and an entry in the sitemap—all at once. Each setting exists, but together they contradict one another. Technical SEO is less about adding more tags than making content, links, index rules, and the preferred URL tell the same story.

Check real examples of at least three page types: an article, a category page, and an admin or search-results page. Checking only the homepage misses template-wide errors.

Give the title, description, and H1 distinct jobs

The SEO title appears in browser tabs and may appear in search results. It should accurately describe the topic and distinguish the page from others. The H1 is the visible main heading; it can be more natural or detailed, but should not describe a different subject. The description helps a searcher decide whether the page is relevant. It is not a keyword dump, and a search engine may choose a different snippet.

Use one clear H1 per page. Do not mark the logo, section name, and article title as separate H1s. Avoid chasing a rigid character count for titles: put the central topic first, keep branding restrained, and check that the meaning is still clear on a phone.

Decide which URL is the preferred version

The same content may be accessible through query parameters, case differences, trailing slashes, print views, or language paths. Choose one stable preferred URL for each version and use rel="canonical" consistently. The canonical target should be an absolute URL that returns 200, is indexable, and genuinely represents the same content.

When duplicate addresses can be permanently consolidated, redirect them. Canonical is a signal, not access control: protect an admin area with authentication, and isolate or mark test pages appropriately rather than hoping a canonical tag hides them. List only preferred, indexable, successful URLs in the sitemap.

Keep robots rules, response codes, and the sitemap consistent

A published article should return 200 and be eligible for indexing. A removed page with no relevant replacement should return 404 or 410; a permanent move should use 301 or 308. A “not found” message delivered with status 200 is a soft 404 that confuses both visitors and monitoring.

robots.txt controls crawling, not guaranteed indexing. Require authentication for private admin pages. Keep drafts and review pages out of public navigation and the sitemap, and mark them noindex where appropriate. Do not block a page in robots.txt while relying on the crawler to read its noindex tag; a blocked crawler may never see that tag.

Match structured data to what readers can see

An article may use Article or BlogPosting data with its real title, author, publication date, update date, and main image. Breadcrumbs may use BreadcrumbList. Do not add ratings, FAQs, or prices that are absent from the page in pursuit of a rich result. Passing a structured-data validator does not guarantee search appearance.

Give each language version its own title, description, and body. Link language alternatives with the correct hreflang values and include a self-reference. Do not rush unreviewed machine translation into the public index while the original language page is complete.

Record the final HTML for each page type

Request the final production HTML, not just the source template. JavaScript behavior, a reverse proxy, and environment variables can make live output differ from a local build.

A minimum pre-release check

Sample at least ten URLs across languages, articles, categories, 404s, and redirects. For each, inspect the response code, indexing directive, canonical, title, and structured data. Check that the sitemap contains no pending, draft, admin, or parameter-based search pages.

Once the technical signals agree, move from tags to evidence. Use the first 30 days after launch plan to distinguish crawling, impressions, clicks, and content problems.