70 checks across 8 categories. Mark each item as you verify it against your site.
Ensure every page has a unique, descriptive title tag between 30–60 characters.
Write a compelling meta description of 120–160 characters for each page.
Set a canonical URL to prevent duplicate content issues.
Reference your XML sitemap so search engines can discover all pages.
Add structured data (Organization, WebSite, Article, Product) to help search engines understand your content.
Use exactly one H1 per page and maintain a logical heading hierarchy.
All images must have descriptive ALT text for accessibility and SEO.
Check for broken internal and external links that hurt user experience and SEO.
Configure robots meta tags to control indexing and avoid accidentally blocking pages.
Add hreflang tags for multilingual sites to serve the correct language version.
Include og:title, og:description, og:url, and og:type for social sharing.
Ensure your sitemap is accessible and has been submitted to search consoles.
Make sure /robots.txt is accessible and correctly configured.
Set viewport meta tag with width=device-width for proper responsive rendering.
Use modern formats (WebP, AVIF) and lazy loading to reduce page weight.
Preload fonts and use font-display: swap to prevent invisible text during load.
Configure caching headers (Cache-Control, Expires) to improve repeat visit speed.
Keep external script and stylesheet count under 10 for optimal performance.
Defer or async non-critical scripts to avoid blocking page rendering.
Keep HTML under 100KB and DOM elements under 1000 for fast rendering.
Provide a print-specific stylesheet for better printed page output.
Limit third-party scripts to 2 or fewer domains to reduce bloat and tracking.
Set the lang attribute on the <html> element for screen readers.
Use ARIA landmark roles (navigation, main, banner, contentinfo) for screen reader navigation.
Ensure all interactive elements are reachable and operable via keyboard.
Maintain sufficient color contrast ratios for text readability.
Provide a skip-to-content link as the first focusable element.
Never disable pinch zoom — it violates WCAG and frustrates users.
All form inputs must have associated labels via for/id or aria-label.
All links in the header and footer should be working properly
Serve all pages over HTTPS to encrypt data in transit.
Use a valid SSL certificate with at least 30 days until expiry.
Add the Strict-Transport-Security header to enforce HTTPS connections.
Set a Content-Security-Policy header to prevent XSS and data injection attacks.
Add X-Frame-Options header to prevent clickjacking via iframes.
Set X-Content-Type-Options: nosniff to prevent MIME type sniffing.
Configure Referrer-Policy header to control referrer information sharing.
Set Permissions-Policy header to restrict browser feature access.
Ensure all resources (images, scripts, styles) load over HTTPS.
Check for exposed API keys, tokens, and credentials in client-side code.
Obfuscate email addresses to protect against spam harvesting bots.
All form actions must submit over HTTPS to protect user data.
Protect forms with CAPTCHA, CSRF tokens, or honeypot fields against abuse.
Configure viewport for mobile devices with width=device-width.
Use srcset and sizes attributes to serve appropriately sized images per device.
Ensure all touch targets are at least 44x44px for easy tapping.
Prevent horizontal scrolling by ensuring content fits within the viewport.
Use a base font size of at least 16px to prevent iOS zoom on input focus.
Add a favicon so your site stands out in browser tabs and bookmarks.
Display your logo prominently for brand recognition.
Provide an Open Graph image for rich link previews on social media.
Configure twitter:card meta tag for Twitter link previews.
Add a twitter:image for Twitter Card visual previews.
Link a manifest.json for installable web app behavior on mobile.
Set theme-color meta tag for branded browser UI on mobile.
Create a custom 404 page that helps users find their way back.
Display a privacy policy compliant with GDPR, CCPA, and other regulations.
Provide terms of service to establish legal boundaries for site usage.
Disclose cookie usage with a clear cookie policy or consent mechanism.
Make contact information easily accessible for user trust and legal compliance.
Display a copyright notice in the footer to protect your content.
Implement a cookie consent banner for GDPR/ePrivacy compliance.
Publish an accessibility statement to demonstrate inclusive design commitment.
Use question-phrased headings ("What is...", "How to...") to capture answer snippets.
Follow each heading with a concise answer paragraph under 200 characters.
Use bulleted or numbered lists for scannable, extractable content.
Use <dl> elements for term-definition pairs to aid answer extraction.
Keep paragraphs under 40 words on average for answer engine readability.
Avoid skipping heading levels (e.g., h1 to h3) for proper content structure.
Add FAQPage, QAPage, or HowTo structured data for answer engine visibility.