Test the URLs that matter most for organic search: key landing pages, service pages, category pages, articles and other indexable resources.

Important pages should normally return a successful

Your robots.txt file should reflect your actual crawl strategy. Make sure rules are not unintentionally preventing search engines from accessing important sections of the site.

Remember that crawl control and indexing control are different. Blocking a URL in robots.txt does not automatically guarantee that the URL disappears from search results.

Search engines may need access to CSS, JavaScript, images and other resources to understand how a page renders and functions.

Avoid blocking files that materially affect layout, navigation, primary content or mobile usability. A page that looks complete to users but incomplete to crawlers can create misleading technical signals.

Internal links should lead users and crawlers directly to useful destinations. Find links pointing to deleted URLs, broken pages or unnecessary redirect chains.

When a better destination exists, update the original internal link instead of depending permanently on redirects.

Important pages should be discoverable through the normal site architecture rather than relying only on an XML sitemap.

Look for orphan pages and weakly connected URLs. Our

Filters, faceted navigation, calendars, internal search pages and tracking parameters can create thousands of low-value URL combinations.

Decide which URL variants deserve to be crawlable and indexable. Prevent uncontrolled parameter combinations from creating duplicate or near-duplicate crawl paths.

Review meta robots directives and other indexing controls on important pages. Valuable URLs should not accidentally carry

Pay particular attention after migrations, redesigns, staging deployments and plugin changes, because temporary indexing rules can sometimes remain in production.

Canonical tags help search engines understand which URL represents the preferred version of duplicate or near-duplicate content.

Important standalone pages should usually reference the intended canonical URL. Avoid contradictory signals where canonicals, redirects, internal links and XML sitemaps point to different versions.

Your website should resolve consistently to one preferred protocol and hostname. HTTP, HTTPS, www and non-www variants should not compete as separate indexable versions.

Use clean permanent redirects and make sure internal links, canonical tags and sitemaps all support the same preferred URL structure.

Your XML sitemap should contain the URLs you actually want search engines to discover and index.

Remove redirected, duplicate, noindex, broken and parameter-driven URLs. Sitemap entries should normally resolve successfully and support the same preferred URLs used by canonical tags and internal links.

Duplicate content can appear through parameters, print versions, pagination, archives, alternate URL paths and CMS-generated variants.

Decide which version should be indexed, then align canonicals, redirects, internal links and sitemap inclusion around that preferred URL.

Use Google Search Console to compare the pages you expect to be indexed with the URLs Google actually reports as indexed, excluded or problematic.

Pay attention to unexpected exclusions, duplicate canonical selections, crawled-but-not-indexed pages and important URLs that disappear after site changes.

Priority pages should not be buried unnecessarily deep inside the site. Important commercial, category and informational pages should be reachable through clear navigation and contextual internal links.

Review pages requiring many clicks from the homepage or major category hubs. Excessive depth can make discovery harder and usually signals an opportunity to improve site architecture.

An orphan page has no meaningful internal-link path from the normal crawlable structure of the website. Search engines may discover it through a sitemap or external link, but it remains weakly integrated with the rest of the site.

Compare crawl data, XML sitemaps, analytics and Search Console URLs to identify disconnected pages. Add useful contextual links where the page still deserves to exist.

See our

Internal anchor text should help users understand what they will find after clicking. Descriptive anchors also give search engines useful contextual information about the destination page.

Avoid relying heavily on vague phrases such as “click here” or “read more” when a natural, descriptive phrase would provide better context. Keep anchor text useful rather than forcing exact-match keywords unnaturally.

Not every page deserves the same level of internal-link support. Important commercial pages, cornerstone resources and high-value informational URLs should receive relevant links from related content across the site.

Review whether authority is concentrated on old or low-value pages while strategic pages remain weakly connected. Strengthen contextual pathways where the relationship is genuinely useful to readers.

Broken internal links interrupt navigation, weaken crawl paths and create unnecessary friction for both users and search engines.

Regularly crawl the site for internal links returning 404, 410 or server-error responses. Update links to the correct destination, restore valuable missing pages, or remove links that no longer serve a useful purpose.

Organize pages into logical topic and business groups so users and search engines can understand how sections relate to one another.

Use consistent navigation, category structures, breadcrumbs and contextual links to reinforce hierarchy. Avoid creating disconnected collections of pages that compete without a clear parent, hub or topic relationship.

Every important indexable page should have a title that clearly describes its primary topic and distinguishes it from competing pages on the same website.

Avoid duplicate titles, vague labels and unnecessary keyword repetition. Keep titles useful for searchers first while naturally reflecting the page’s main search intent.

Meta descriptions do not guarantee rankings, but strong descriptions can improve how a page is presented in search results and help users understand why the result is relevant.

Write concise, specific descriptions for high-value pages. Avoid copying the same description across many URLs or stuffing keywords unnaturally.

Headings should organize the page into understandable sections. Use the main heading for the primary page topic, then structure supporting sections with logical subheadings.

Do not use heading levels only for visual styling. The hierarchy should make sense when read as an outline and should help users scan long-form content efficiently.

URLs should communicate the topic clearly without unnecessary parameters, session IDs, dates or deeply nested folders unless those structures genuinely help users.

Avoid changing established URLs simply to make them shorter. When a change is necessary, use a permanent redirect and update internal links so the new address becomes the site’s primary reference.

Multiple pages targeting nearly identical intent can compete with one another and make it harder for search engines to determine which URL should rank.

Compare overlapping pages and decide whether they should be differentiated, consolidated, redirected or canonicalized. Keep the strongest URL aligned with the clearest search intent.

Large images can slow down otherwise well-optimized pages. Resize images appropriately, use efficient formats where practical and avoid serving files far larger than their displayed dimensions.

Add useful alternative text when an image contributes meaning to the page. Decorative images do not need keyword-stuffed descriptions.

The title, main heading, introductory content, internal anchor text and overall page purpose should reinforce the same primary topic.

Do not optimize individual elements in isolation. Strong technical on-page SEO comes from consistent signals that accurately describe what the page delivers to the searcher.

Largest Contentful Paint measures how quickly the main visible content becomes available to the user. Slow hero images, server response times, render-blocking resources and oversized page elements can delay this experience.

Identify the actual LCP element on important templates and optimize the resources that directly affect it rather than applying generic speed fixes across the entire site.

Interaction to Next Paint reflects how responsive a page feels when users click, tap or interact with controls.

Investigate long JavaScript tasks, expensive event handlers, excessive third-party scripts and main-thread work that delays visible feedback after an interaction.

Cumulative Layout Shift measures unexpected movement of visible page elements while the page loads or changes.

Reserve space for images, advertisements, embeds and dynamic components. Avoid inserting content above existing elements after the user has started reading or interacting with the page.

Important pages should remain readable, usable and fully functional on smaller screens. Check navigation, forms, tables, buttons, images and interactive elements on actual mobile devices rather than relying only on desktop resizing.

Look for horizontal overflow, tiny tap targets, overlapping elements, oversized headings and content that becomes difficult to scan on narrow screens.

Large JavaScript bundles, unused libraries and excessive third-party scripts can delay rendering and make interactions feel slow.

Remove code that does not contribute to the page, defer non-critical scripts where appropriate and review plugins or widgets that add significant front-end work without enough user value.

Slow server responses affect every resource that follows. Review hosting performance, application processing, database queries, caching behavior and recurring server errors on important pages.

Use appropriate page, object and browser caching while making sure dynamic or personalized content is not cached incorrectly.

The resources needed to display meaningful above-the-fold content should not compete unnecessarily with low-priority scripts, fonts, widgets or third-party integrations.

Review render-blocking CSS, font loading, important images and resource ordering so useful content becomes visible and usable as early as practical.

Structured data should accurately describe information users can actually see on the page. Do not add schema simply because a markup type exists or because a plugin makes it easy to enable.

Use appropriate schema types for the page and keep names, URLs, dates, authors and other properties consistent with the visible content.

Breadcrumbs help users understand where a page sits within the wider site structure and can reinforce the relationship between sections, categories and individual pages.

When breadcrumb structured data is used, make sure the markup follows the same hierarchy that users see on the page.

Test important templates after adding or changing structured data. Syntax errors, missing required properties and conflicting markup can prevent search engines from understanding the intended entity information.

Recheck markup after theme, plugin or template changes because valid structured data can break when surrounding HTML changes.

Search appearance should accurately communicate what the page offers. Review important URLs for unclear titles, weak snippets, unexpected dates, missing branding or other presentation problems that could reduce qualified clicks.

Do not optimize snippets only for higher click-through rates. The promise made in search results should match the experience users receive after landing on the page.

Structured data can become invalid after theme, plugin or template changes even when the visible page still appears normal.

Monitor important page types for new markup errors and eligibility changes. Treat rich-result enhancements as optional presentation opportunities rather than guaranteed search features.

Open Graph and other sharing metadata help control how important pages appear when shared through social platforms, messaging apps and other services that generate link previews.

Check titles, descriptions and preview images on major landing pages. Use clear branded images and avoid outdated or missing assets that weaken presentation when content is shared.

Regularly review indexing reports for important pages that disappear from Google’s index, become excluded unexpectedly or develop new crawl and canonicalization problems.

Focus on patterns rather than isolated URLs. Sudden increases in excluded, duplicate, redirected or not-indexed pages can reveal template, migration or configuration problems affecting entire sections.

Recurring 404, 5xx, timeout and DNS errors can interrupt crawling and damage user experience. Important URLs should remain consistently accessible rather than working only intermittently.

Separate genuine removed pages from accidental failures. Restore important content, correct broken links and investigate infrastructure problems when server errors affect multiple URLs.

Review Google Search Console for manual actions and security warnings. Hacked content, malware, deceptive pages or serious guideline violations can affect search visibility far more than ordinary optimization issues.

If a warning appears, resolve the underlying cause first, verify the affected areas thoroughly and follow the appropriate review or reconsideration process when required.

All important pages and resources should load securely over HTTPS without mixed-content warnings, certificate errors or unnecessary redirects between protocol versions.

Check canonical URLs, internal links, sitemaps, structured data and redirects so they consistently reference the preferred HTTPS version of each URL.

Theme updates, application releases, migrations, plugin changes and infrastructure work can introduce technical SEO regressions even when pages still appear visually correct.

After significant deployments, recheck crawlability, index directives, canonicals, redirects, structured data, internal links, page status codes and critical templates.

A technical SEO task is not complete when code is deployed. Confirm that the affected live URLs now return the intended status, markup, indexation signals and user experience.

Re-crawl representative pages and use Search Console or other relevant tools to verify that the original problem has actually been resolved.

Do not treat every technical SEO issue as equally urgent. Problems that block crawling, indexing, rendering, usability or important conversion paths should be addressed before minor presentation improvements.

Combine technical severity with affected traffic, business value and the number of URLs involved to create a practical implementation order.

Technical improvements should eventually produce measurable changes in crawling, indexing, visibility, engagement or conversions. Record important changes and compare performance before and after implementation.

Use Search Console, analytics and crawl data together rather than relying on a single SEO score.

Maintain a record of discovered issues, affected URLs, implementation status and validation results. This prevents recurring problems from being rediscovered without context during every audit.

A useful technical SEO process shows what was fixed, what remains open and whether previously resolved problems have returned.

After migrations, redesigns, URL changes or major SEO fixes, crawl representative sections again instead of assuming the implementation worked as intended.

Compare status codes, canonicals, index directives, internal links and crawl depth before and after the change. New technical problems sometimes appear while another issue is being repaired.

Important technical requirements should not depend entirely on occasional manual audits. Build repeatable checks for critical templates and URLs where practical.

Monitor accidental noindex directives, broken canonicals, redirect failures, server errors, missing metadata and other high-impact changes that could silently affect search visibility.

Technical SEO is not a one-time project. Websites change as content, plugins, templates, infrastructure and application code evolve.

Schedule recurring reviews and perform additional focused audits after migrations, redesigns, major releases or unusual search-performance changes. Compare each audit with the previous one so progress can be measured instead of restarting from zero.