1. Crawlability and indexation
Before search engines can rank a page, they must be able to find and read it. Crawlability refers to whether Googlebot can reach a page at all; indexation refers to whether the page is added to Google’s index and eligible to rank.
- robots.txt. Check that your robots.txt file does not accidentally block important pages or directories. A common mistake is disallowing the
/wp-admin/folder in a way that also blocks CSS or JavaScript the renderer needs. - XML sitemap. Every indexable URL should appear in a sitemap, submitted to Google Search Console. Keep the sitemap clean: only include canonical, indexable URLs, not pagination variants or filtered pages.
- noindex tags. Audit for pages carrying a
meta name="robots" content="noindex"tag that should be ranking. This often happens when a development setting is not removed before launch.
2. Canonical tags
A canonical tag tells search engines which version of a page is the primary one. Without it, duplicate content, such as a URL with and without a trailing slash, or with and without query parameters, can split ranking signals across multiple URLs.
- Every page should have a self-referencing canonical unless it is intentionally a duplicate pointing elsewhere.
- Canonical URLs should be absolute (include the full domain), use HTTPS, and match the canonical version exactly (trailing slash consistent with how the URL is served).
- Pagination and filtered pages on ecommerce sites are common sources of canonical errors. Each page variant should either carry a canonical to the main page or be blocked from indexation.
3. Structured data
Structured data is code that describes the content of a page to search engines and AI systems in a standardised format. It powers rich results in Google Search and improves how AI engines summarise and cite your content.
- Organization schema on the homepage, covering name, URL, logo, and contact information.
- FAQPage schema for pages with questions and answers, which can appear as expanded FAQ rich results in search.
- Article or BlogPosting schema on editorial content, including datePublished and dateModified, which help AI engines understand content freshness.
- Product schema on ecommerce product pages, including price, availability, and reviews where present.
4. HTTPS and security
HTTPS is a baseline requirement. All pages should be served over HTTPS, with HTTP requests redirecting to the HTTPS version. Mixed content, where an HTTPS page loads HTTP resources such as images or scripts, can trigger browser warnings and negatively affect trust signals.
Check that the SSL certificate covers all subdomains in use (or uses a wildcard certificate), and confirm the certificate expiry date is monitored so it does not lapse silently.
5. Page speed and Core Web Vitals
Technical SEO and page speed overlap significantly. Google’s Core Web Vitals (LCP, INP, CLS) are both performance benchmarks and ranking signals. The main technical contributors to slow pages are:
- Render-blocking scripts loaded synchronously in the
<head>. - Uncompressed or oversized images (use WebP/AVIF and compress before upload).
- Unused CSS and JavaScript included in the initial page load.
- No caching headers, so returning visitors fetch the full page each time.
6. Internal linking
Internal links pass ranking signals between pages and help search engines understand site hierarchy. Important pages should receive more internal links than less important ones.
Use descriptive anchor text that describes the target page. Generic anchors like “click here” or “learn more” waste the opportunity to reinforce the target page’s relevance for specific topics.