A technical seo checklist should help you find and fix the issues that prevent search engines from crawling, understanding, indexing, and serving your pages. Work in this order: establish a baseline, audit crawl and indexation, repair site architecture and duplicate URLs, check rendering and page experience, validate on-page signals, then monitor the changes in Search Console and analytics.
This workflow is designed for a growing business website, online store, international site, or agency-managed account. It prioritizes problems that can suppress many URLs at once rather than spending the first day polishing isolated metadata.
Establish the audit scope and baseline
Start by defining which site, subdomain, country, device type, and business outcome the audit covers. A Bangladesh-focused service site, a multilingual ecommerce store, and a site recovering from a ranking loss need different checks. Record the baseline before making changes so you can distinguish a technical improvement from a seasonal traffic shift or campaign effect.
Collect evidence before changing URLs
Use Google Search Console to export performance data by page, query, country, and device. Its documentation explains that the Performance report includes metrics such as clicks, impressions, click-through rate, and average position; use the official Search Console Performance report documentation when interpreting those fields.
- List the top landing pages by organic clicks and revenue or leads.
- Record pages with high impressions but weak click-through rate.
- Separate branded and non-branded queries where possible.
- Note the date of any migration, redesign, template change, manual action, or traffic loss.
- Save the current sitemap URLs, robots.txt file, analytics annotations, and index coverage exports.
For a small site, an illustrative starting policy is to review the previous 16 weeks and compare them with the same period in the previous year. Adjust that window when seasonality, a recent launch, or a short sales cycle makes the comparison misleading. The signal to change the policy is unstable demand rather than a fixed number of weeks.
| Audit question | Evidence to collect | Decision |
|---|---|---|
| Which pages matter commercially? | Organic landing pages, conversions, revenue, assisted conversions | Protect and prioritize these URLs first |
| Where did visibility change? | Search Console clicks, impressions, queries, countries, devices | Compare affected templates, not just individual pages |
| What can search engines discover? | Crawl export, XML sitemap, internal links, robots.txt | Remove accidental barriers before rewriting content |
| Which URLs should exist? | Indexable URL inventory and canonical targets | Consolidate duplicates or improve valuable thin pages |
Audit crawling and indexation
Next, determine whether important URLs can be discovered, fetched, and indexed. A page can be technically reachable in a browser yet still be excluded from search because of a noindex directive, an incorrect canonical, authentication, a blocked resource, or a weak discovery path.
Check the control points in order
- Robots.txt: confirm that it does not block important sections, JavaScript, CSS, images, or an entire staging pattern accidentally exposed on production.
- HTTP status: identify unexpected 5xx errors, redirect chains, soft 404 behavior, and pages that return a successful status while displaying an error.
- Index directives: inspect meta robots and X-Robots-Tag responses. Confirm that noindex is intentional on filters, internal search results, account pages, and duplicate utility URLs.
- XML sitemaps: include only canonical, indexable, successful URLs that you want discovered. Google describes sitemaps as a way to provide information about pages, images, videos, and other files to help crawling; see its sitemap overview.
- Internal discovery: verify that important pages have crawlable links from relevant navigation, category, editorial, or contextual pages.
Do not treat “submitted in a sitemap” as proof of indexation. Use URL Inspection on representative URLs from every important template: homepage, category, product, service, blog, location, and translated page. Compare the inspected canonical, user-declared canonical, indexing status, and last crawl.
Useful rule: a sitemap tells search engines what you consider important; internal links and page relationships help show why those URLs matter.
For a site with 10,000 or fewer indexable URLs, an illustrative starting policy is to inspect at least one sample from every template and every major country or language folder. Increase the sample when the same template produces different behavior by market. The signal for expanding the sample is variation in status, canonical, rendering, or traffic—not the URL count alone.
Repair site architecture, redirects, and duplicate URLs
Once basic access is clear, decide which URL is the preferred version of each page. Duplicate URLs commonly arise from tracking parameters, faceted navigation, trailing-slash differences, HTTP-to-HTTPS transitions, case variations, print pages, and international alternatives.
Choose consolidation based on user intent
Use a permanent redirect when the old URL has been replaced and visitors should land on the new page. Use a canonical link when multiple accessible versions are useful or unavoidable but one version should represent the group. Use noindex cautiously for pages that users need but should not appear in search. These controls are not interchangeable.
Google’s documentation explains that canonicalization helps select a representative URL among duplicate or very similar pages; use the official duplicate URL consolidation guidance when choosing between redirects, canonicals, and other signals.
For ecommerce, do not automatically canonicalize every filter page to the category page. A filter that represents a meaningful search demand—such as “women’s waterproof hiking boots”—may deserve its own optimized landing page. A parameter that merely sorts products by price usually does not. The decision depends on distinct demand, inventory stability, useful content, and conversion intent.
Worked example: an ecommerce category
Suppose an online store has these URLs:
/shoes/hiking//shoes/hiking/?color=black/shoes/hiking/?sort=price-low/shoes/hiking/black-waterproof/
The base category may be the canonical commercial page. The sort URL can remain a user utility URL without entering the sitemap. The color filter may be consolidated if it adds no distinct value. The black waterproof URL may deserve indexation if it has stable products, unique copy, useful title and headings, and measurable demand. Document this decision in the implementation ticket instead of applying one rule to every parameter.
For redirects, an illustrative starting policy is to flag chains longer than one redirect and loops immediately. Adjust that policy when a platform or migration makes a direct mapping impractical, but require a reason and test the final destination. The signal is not merely chain length; it is whether users and crawlers reach the intended relevant page reliably.
Check rendering, mobile experience, and performance
Technical SEO is not only a server-response exercise. Important content, links, prices, and structured data should be available in the rendered page that search engines and users receive. Compare the raw HTML with the rendered DOM for JavaScript-heavy templates, especially product listings and application-style websites.
- Confirm that primary content is not revealed only after an interaction that search engines cannot reliably trigger.
- Test navigation, menus, tabs, accordions, and pagination on mobile.
- Check that product price, availability, service area, and contact details render consistently.
- Look for blocked or failed JavaScript and CSS resources.
- Review templates with real devices and throttled connections, not only a fast office connection.
Use PageSpeed Insights and field data where available, but treat performance as a prioritization input rather than a magic ranking score. Google’s Core Web Vitals guidance describes the user-focused metrics used to assess loading, responsiveness, and visual stability. A page can need work even when its score looks acceptable, and a high score cannot compensate for blocked crawling or irrelevant content.
Prioritize fixes that affect valuable templates: oversized hero media, excessive third-party scripts, layout shifts caused by missing dimensions, and slow server responses on product or lead-generation pages. An illustrative starting policy is to investigate templates with repeated field-data failures rather than chasing a single laboratory outlier. Change the policy when real-user data is sparse or the page’s conversion path shows a different bottleneck.
Validate content signals and structured data
Technical fixes should make the right content easier to understand, not hide weak content behind cleaner code. Check that each indexable page has a distinct purpose, a descriptive title, a useful main heading, accessible text, and internal links to the next sensible action.
Run a template-level on-page review
- Titles and descriptions: describe the actual page and its benefit without repeating the same phrase across every URL. Use the meta description length checker to catch truncation risks, then prioritize accuracy over a character target.
- Headings: make the page topic and sections understandable to customers, not just crawlers.
- Images: use descriptive alternative text when the image conveys information; avoid stuffing keywords into decorative image text.
- Internal links: connect supporting guides to services, categories, products, and location pages with contextually useful anchor text. Find candidates with the internal link opportunity tool.
- Structured data: mark up information that is visible and accurate on the page, then validate it against the relevant search feature requirements.
Google explains that structured data helps it understand page content and may make pages eligible for specific search result features, but eligibility is not a guarantee of enhanced display; consult the structured data introduction. Do not add review, product, organization, or local business properties merely because a plugin offers them. Every value should describe the page and comply with the relevant guidelines.
For an international business, check language and regional signals together. Confirm that translated pages are genuinely translated, currency and availability match the target market, and hreflang references are reciprocal and reachable. A Bangladesh landing page should not promise service coverage that the business cannot provide; technical accuracy cannot repair a market-intent mismatch.
Prioritize fixes, deploy safely, and monitor
Turn the audit into a release plan rather than a spreadsheet of warnings. Rank each issue by affected URLs, business value, confidence in the diagnosis, implementation effort, and reversibility. A missing canonical on a revenue-driving template usually outranks a minor heading inconsistency on one old article.
| Priority | Typical issue | Action | Verification |
|---|---|---|---|
| Urgent | Important section blocked, widespread noindex, server errors | Pause related releases and correct the access problem | Live test, crawl sample, Search Console inspection |
| High | Wrong canonical, broken migration redirects, duplicate commercial pages | Map preferred URLs and deploy controlled rules | Redirect test, canonical check, indexation trend |
| Medium | Weak internal linking, slow shared template, incomplete structured data | Fix the template or highest-value page group | Rendered crawl, field data, rich-result validation where relevant |
| Low | Isolated metadata inconsistency or obsolete utility URL | Bundle with the next content or maintenance release | Spot-check and document the outcome |
Use an illustrative starting policy of one controlled release at a time for a major migration or template change. If the site has strong staging, rollback, and monitoring processes, several related fixes may be grouped. The signal to split the release is uncertainty about causation: if traffic drops, you need to know which change introduced the problem.
After deployment, recrawl representative URLs and annotate the release date in analytics. Monitor organic clicks, impressions, indexed pages, crawl errors, conversions, and revenue by template and market. Do not declare success from rankings alone; a ranking increase with fewer qualified leads may indicate a targeting or conversion problem.
Do this first: build the evidence-led fix queue
On your next working session in 2026, export Search Console performance data, crawl the live site, and create one row for every issue with its affected template, preferred outcome, owner, and verification test. Start with accidental access barriers and wrong URL consolidation, then address rendering and internal linking before polishing individual snippets.
If the site has lost visibility, spans multiple markets, or cannot turn audit findings into safe implementation tickets, Mr Haq can help with technical SEO strategy, recovery planning, reporting, and international or local search prioritization through Mr Haq.
Authored with NotFair SEO
