Overview
This Framework provides a structured approach to validate the technical health of your website for search engines. Technical SEO (Search Engine Optimization) makes sure search engines can find, crawl, understand, and rank your pages. When it breaks, even great content can lose visibility, traffic, and revenue.
This Framework aligns with ObservePoint capabilities, but it also suggests processes, documents, and policies that we recommend an organization consider in its pursuit of excellence.
Checks reference Google Search Central documentation. Principles apply across other search engines such as Bing.
Framework
This Framework is organized into the following Policies:
Site Access & Availability - Status codes, broken links, redirects, HTTPS, and sitemaps
Search Visibility & Metadata - Page titles, H1 headings, meta descriptions, social titles, canonical URLs, robots directives, hreflang, and URL structure
Page Experience - Core Web Vitals and mobile readiness
Content & Structured Data - Image alt text, content length, and structured data
Documentation & Processes - Recommended documents and governance processes
Each policy contains individual Checks.
For each Check, we include links to pre-built reports in the ObservePoint Platform (when possible) and an implementation & remediation guide.
Each check is accompanied by an icon:
The ✅ icon represents a Check that is available out of the box by just running an Audit.
The 🛠️ ✅ icons represent a Check that requires additional configuration. Most of these use the SEO check script, an on-page action you add to your Audit once. It checks page HTML tags such as meta descriptions and canonical URLs, and writes any issues to the Browser Logs report.
In addition to checks, there are recommended documents (📄) and processes (⚖️) we encourage you to maintain as part of an effective governance program.
Note: ObservePoint measures your pages the way a browser sees them during a scan (lab data). Google ranks pages partially on real-user data (field data), which you can find in Google Search Console. Use ObservePoint to catch issues early and at scale, and Search Console to confirm how Google sees your site.
Scope & Frequency
Before diving into the specifics of each policy, we want to provide our recommendation around the scope and frequency of validating your technical SEO.
Frequency | Scope | Goal |
Daily | 10-100 most critical pages (highest organic traffic, top landing pages, key product pages) | Confirm your most valuable search pages are live, fast, and indexable |
Every Deployment | 10-15% of pages or 100% of templates | Ensure new code, CMS changes, or migrations haven't broken titles, canonicals, redirects, or robots directives |
Quarterly | 100% of pages, plus your XML sitemap | Catch "long tail" issues such as orphaned broken pages, outdated redirects, and missing metadata |
If you're not sure how many pages exist on your domain, ask your Success Manager or our Support Team about running a Site Census scan.
Site Access & Availability
This policy represents checks that make sure search engines (and your visitors) can reach every page you want found.
✅ All pages return a "Success" status code
Broken pages (0, 400, or 500 level status codes) can't be indexed and end the visitor's journey. When important pages return errors, search engines may drop them from results, and the links pointing to them lose their value.
Implementation & Remediation Guide: Link coming soon
Source citation: How HTTP status codes affect Google Search
✅ No broken links
Links that point to broken pages waste search engine crawl budget and frustrate visitors. They also signal a poorly maintained site.
Implementation & Remediation Guide: Link coming soon
Source citation: Link best practices
✅ Redirects are direct (no redirect chains)
Each extra redirect hop slows the page down and makes it harder for search engines to follow. Redirects should point straight to the final URL in a single hop.
Note: When your site links to its own pages, link straight to the final URL instead of going through a redirect. Redirects are there so that old URLs and links from other sites keep working
Implementation & Remediation Guide: Link coming soon
Source citation: Redirects and Google Search
✅ All pages are served over HTTPS
HTTPS protects your visitors and is part of Google's page experience signals. Pages that load over HTTP, or HTTPS pages that redirect back to HTTP, should be fixed.
Implementation & Remediation Guide: Link coming soon
Source citation: HTTPS as a ranking signal
🛠️ ✅ XML sitemap only lists live pages
Your sitemap tells search engines which pages matter most. Broken or redirected URLs in your sitemap waste crawl budget and reduce trust in the sitemap. To validate this, create an Audit that uses your XML sitemap as its starting URLs, then review broken and redirected pages from that Audit.
Implementation & Remediation Guide: Link coming soon
Source citation: Learn about sitemaps
Search Visibility & Metadata
This policy represents checks that help search engines understand each page and decide how to show it in results.
✅ Every page has a unique, descriptive title
The page title is often the headline shown in search results. Missing, duplicate, or very long titles reduce click-through rates and make it harder for search engines to tell your pages apart. We recommend titles between 10 and 65 characters.
Implementation & Remediation Guide: Link coming soon
Source citation: Influencing your title links
🛠️ ✅ Every page has a meta description
A clear meta description helps search engines create a useful snippet and encourages clicks. We recommend keeping descriptions under 155 characters so they aren't cut off.
Implementation & Remediation Guide: Link coming soon
Source citation: Control your snippets in search results
🛠️ ✅ Every page has an H1 heading
The H1 is the main heading on the page. It helps visitors and search engines understand what the page is about, and helps screen reader users find their way around.
Implementation & Remediation Guide: Link coming soon
Source citation: SEO Starter Guide
🛠️ ✅ Pages include a social sharing title
Open Graph and Twitter title tags control the headline people see when your page is shared on social media. They don't affect search rankings, but they help shared links look right and get clicks.
Implementation & Remediation Guide: Link coming soon
Source citation: The Open Graph protocol
🛠️ ✅ Canonical URLs are present and resolve successfully
Canonical tags tell search engines which version of a page is the "main" one, preventing duplicate content issues. A canonical URL that points to a broken page sends search engines to a dead end.
Implementation & Remediation Guide: Link coming soon
Source citation: How to specify a canonical URL
🛠️ ✅ Robots directives are intentional
*Manual review required.
A "noindex" robots meta tag removes a page from search results. It's useful for pages like internal search results or thank-you pages, but a single misplaced tag on a key template can remove whole sections of your site from Google.
Implementation & Remediation Guide: Link coming soon
Source citation: Robots meta tag specifications
🛠️ ✅ Hreflang URLs resolve successfully
For multilingual or multi-regional sites, hreflang tags point search engines to the right language version of a page. If those URLs are broken, visitors may see the wrong language or region in search results.
Implementation & Remediation Guide: Link coming soon
Source citation: Tell Google about localized versions of your page
🛠️ ✅ URLs are simple and readable
Short, lowercase URLs that use hyphens instead of underscores or spaces are easier for people to read and share. URLs are case-sensitive, so mixed case can create duplicate versions of the same page.
Implementation & Remediation Guide: Link coming soon
Source citation: URL structure best practices for Google
Page Experience
This policy represents checks that pertain to page speed, visual stability, and mobile readiness. Learn more in the ObservePoint Web Vitals Guide. Also, more documentation on page experience and web vitals is available here.
✅ Largest Contentful Paint (LCP) is under 2.5 seconds
LCP measures how quickly the main content of a page appears. It is one of Google's Core Web Vitals, and slow pages tend to rank and convert worse.
Implementation & Remediation Guide: Link coming soon
Source citation: LCP
✅ Cumulative Layout Shift (CLS) is under 0.1
CLS measures how much content moves around while the page loads. Jumpy pages frustrate visitors, and CLS is one of Google's Core Web Vitals.
Implementation & Remediation Guide: Link coming soon
Source citation: CLS
✅ Time to First Byte (TTFB) is under 0.8 seconds
TTFB measures how quickly your server responds. A slow server delays everything else on the page, so it's usually the first speed issue to fix.
Implementation & Remediation Guide: Link coming soon
Source citation: Time to First Byte
✅ First Contentful Paint (FCP) is under 1.8 seconds
FCP measures how quickly the first text or image appears on the page. Until then, visitors see a blank screen and may leave. FCP isn't one of Google's Core Web Vitals, but a slow FCP almost always means a slow LCP, so it helps you find the cause.
Implementation & Remediation Guide: Link coming soon
Source citation: First Contentful Paint
🛠️ ✅ Pages include a mobile viewport tag
Google indexes the mobile version of your pages first. Without a viewport meta tag, pages may not display properly on phones.
Implementation & Remediation Guide: Link coming soon
Source citation: Mobile-first indexing best practices
Content & Structured Data
This policy represents checks that help search engines understand what each page is about.
✅ Images have descriptive alt text
Alt text helps search engines understand images and helps your images appear in image search. Google calls it the most important attribute for describing an image. It also supports accessibility (see our ADA Web Compliance Framework).
Implementation & Remediation Guide: Link coming soon
Source citation: Image SEO best practices
🛠️ ✅ Review pages with very little content
Google doesn't have a preferred word count, but pages with very little text may not answer a visitor's question. Use the word count to find thin pages, especially blog posts and articles, and review them.
Implementation & Remediation Guide: Link coming soon
Source citation: Creating helpful, reliable, people-first content
🛠️ ✅ Key pages include structured data (JSON-LD)
Structured data describes your content (products, articles, events, FAQs) in a format search engines can read, and can make your pages eligible for rich results, such as star ratings or prices in search. It isn't needed on every page, so focus on the templates that match a rich result type. Google recommends the JSON-LD format.
Implementation & Remediation Guide: Link coming soon
Source citation: Introduction to structured data
🛠️ ✅ Structured data (JSON-LD) is valid
Structured data that can't be read, or that's missing required fields, won't be used for rich results. Template or CMS changes can break it without any visible change on the page.
Implementation & Remediation Guide: Link coming soon
Source citation: Introduction to structured data
Documentation & Processes
This policy represents recommended documents and processes pertaining to technical SEO.
📄 Create and maintain SEO template standards
A short document that defines the rules for every page template: title and meta description formats, canonical rules, heading structure, and which pages should be "noindex." This gives developers and content teams one source of truth and makes it easy to spot when a page breaks the rules.
📄 Maintain a redirect map
A log of every URL change and where it now redirects. This prevents redirect chains, protects search rankings during site migrations, and makes it easy to clean up outdated redirects. ObservePoint can help you build and maintain one.
⚖️ Prioritize your most important pages
Use Google Search Console or your analytics to find the pages that bring in the most organic traffic and revenue. Include them in your daily Audit and fix their issues first.
⚖️ Implement a pre-launch SEO check
Run an ObservePoint Audit on staging or newly deployed templates before (or right after) every release and site migration. Confirm that titles, canonicals, robots directives, and redirects match your template standards before search engines find the problem.
⚖️ Review Google Search Console regularly
Search Console shows how Google actually crawls and indexes your site, including real-user Core Web Vitals. Pair a monthly Search Console review with your ObservePoint Audits so you catch issues early and confirm fixes are working.
Conclusion
This framework gives you a solid technical foundation for search. By monitoring it with ObservePoint, you can make sure search engines can reach your pages, understand them, and show them to the right people, so your content has the best chance to rank.
