Technical SEO Checklist: 25 Checks Before You Publish Anything

Why use a technical SEO checklist before publishing?

A technical SEO checklist protects the work you put into content. A beautifully written page that is accidentally set to noindex, blocked in robots.txt or buried six clicks deep will earn nothing. Running the checks before you publish, and again after major changes, catches those faults early.

The 25 checks below are grouped into five areas. You do not need special software for most of them: Google Search Console, a browser and a free crawler are enough to start. If you are new to the wider topic, our guide on what SEO is gives the background.

Which crawling and indexing checks come first?

Start here, because a page that cannot be crawled or indexed cannot rank. Open Search Console and use the Pages report and URL Inspection tool to confirm what Google sees.

Use a spreadsheet to track each check as pass, fail or not applicable, with the URL, owner and date fixed. That record turns a one-off clean-up into a repeatable process, and it makes it easy to hand the work to a developer with clear instructions rather than vague requests.

• 1. robots.txt does not block important folders, CSS or JavaScript files.
• 2. No important page carries a noindex tag or noindex header by mistake.
• 3. An XML sitemap exists, lists only canonical, indexable URLs and is submitted in Search Console.
• 4. Canonical tags point to the preferred version of each page and are not self-contradicting.
• 5. Only one version of the site resolves: http redirects to https and www and non-www are consolidated.
• 6. Key pages appear as indexed in the URL Inspection tool.
• 7. Duplicate or near-duplicate pages, such as filtered or parameter URLs, are handled with canonicals or noindex as appropriate.

How should site structure and URLs be checked?

Good structure helps crawlers and visitors reach every important page quickly. Think of your site as a tree: home page, categories or services, then detail pages.

Keep important pages within about three clicks of the home page, make sure every page has at least one internal link pointing to it, and avoid navigation that depends entirely on JavaScript events that crawlers may not follow.

• 8. URLs are short, readable, lowercase and use hyphens between words.
• 9. No orphan pages exist, meaning pages with no internal links.
• 10. Important pages are reachable within a few clicks of the home page.
• 11. Breadcrumbs or clear navigation show hierarchy.
• 12. Redirects are single-step 301s with no chains or loops.
• 13. Broken internal links and 404 errors are fixed or redirected where a relevant replacement exists.

What speed and mobile checks matter?

Most Indian users browse on phones, often on variable connections, so mobile experience is not optional. Google also uses mobile-first indexing, meaning it primarily evaluates the mobile version of your pages.

Test key templates in PageSpeed Insights and compare results with real-user data in Search Console. Our explainer on Core Web Vitals covers the metrics in detail.

• 14. The mobile layout shows the same main content as desktop, not a stripped-down version.
• 15. Text is readable and buttons are easy to tap without zooming.
• 16. Images are compressed, correctly sized and use modern formats where supported.
• 17. Images below the fold are lazy-loaded, but the main hero image is not.
• 18. Render-blocking scripts and unused plugins are reduced.
• 19. Core Web Vitals pass for important page templates, or a plan exists to improve them.

Which security, markup and content checks complete the list?

The last group covers trust signals and the signals that tell search engines what each page contains.

If your site uses a content management system such as WordPress, Shopify or Wix, some checks are controlled by settings and plugins rather than code. For example, a single checkbox that discourages search engines from indexing the site can undo months of work. Always look at the live page source or the URL Inspection result, not just the setting you believe you chose, because plugins can override each other.

Also remember staging sites. Development copies should be blocked from indexing, and that block must be removed on the live site at launch. Forgetting this step is one of the most common launch mistakes.

• 20. HTTPS is valid on every page with no mixed-content warnings.
• 21. Each page has a unique title tag and meta description that match its topic.
• 22. One clear h1 per page, with subheadings in a logical order.
• 23. Structured data such as Organization, Article, Product or FAQ is valid in a testing tool and matches visible content.
• 24. Images have descriptive alt text, and key pages have enough original content to satisfy the search intent.
• 25. Hreflang tags are correct if you publish the same content in more than one language or country version.

How do you run the checklist in practice?

Use a simple three-pass routine. In pass one, crawl the site with a free or paid crawler and export errors such as 4xx pages, redirect chains and missing titles. In pass two, compare the crawl with Search Console to see which pages Google has actually indexed and which it has excluded, and why. In pass three, test five representative pages, one from each template type, on a real phone.

Finish by writing a short summary for the business owner: what was wrong, what was fixed, what remains and the expected effect. Plain-language reporting keeps everyone aligned and prevents technical work from being forgotten when priorities shift.

Then prioritise. Fix issues that affect many pages first, such as a site-wide noindex or slow template, before one-off errors. Record what you changed and the date, so if traffic moves you can link cause and effect.

Schedule the checklist: before each launch, after any redesign or migration, after installing major plugins and at least quarterly for a stable site. Websites change quietly, and a developer update can undo earlier fixes without anyone noticing.

When should you get professional help?

Many of these checks are within reach of a careful site owner. Bring in a specialist when you face JavaScript rendering problems, large e-commerce sites with thousands of parameter URLs, a planned migration or unexplained drops in indexed pages. A specialist reads server logs, handles complex redirects and prioritises by business impact.

Our SEO services include technical audits that turn a long list of issues into a ranked action plan. If you would like a second pair of eyes on your site, contact us and we will talk through what to look at first.

Frequently asked questions