Measure SEO with provider evidence, not estimates
OLT brings organization-scoped evidence from Google Search Console, Google Analytics 4, and Bing Webmaster Tools into its SEO workspace. It uses supported provider reports for search performance, organic landing pages, AI referrals, links, indexing, and sitemaps. When a connector cannot supply usable evidence, OLT leaves that measurement unavailable instead of estimating it.
Connector setup
Set up one verified website for SEO measurement
Use SEO Connections to align each provider connection with the public website configured in CMS Delivery, then sync the supported evidence.
Existing OLT users
Sign in if needed, then manage the verified provider connections for your organization.
Open SEO ConnectionsNew to OLT
Create your organization, verify your email, and continue directly to SEO Connections.
Discuss a project-
1
Confirm the prerequisites
Configure the public website in CMS Delivery and use an OLT organization owner or admin who can open SEO Connections. Confirm the Google accounts you will connect can access the verified Search Console and GA4 properties, and that the website is verified in Bing Webmaster Tools.
-
2
Connect Google Search Console
In SEO Connections, authorize the Google account that can access the verified Search Console property, then select that property for measurement.
-
3
Validate the GA4 property
Connect Google Analytics 4, then choose the property with a web stream whose hostname matches the website in CMS Delivery. A matching GA4 web stream is necessary for property validation, but it is not sufficient for live traffic validation.
-
4
Validate live GA4 traffic
The production GA4 tag must record sessions on the CMS Delivery hostname and within its configured path prefix. Conventional www and non-www hosts are equivalent; other subdomains and landing pages outside the prefix are excluded. If this check fails, verify the production tag and stream hostname, correct CMS Delivery when its website URL or path prefix is wrong, or select the property that measures the website.
-
5
Connect Bing Webmaster Tools
Obtain a Bing Webmaster API key under Settings → API access. In SEO Connections, paste that API key and the exact verified site URL as Bing lists it, then choose Save to test the connection. OLT saves it only when the key can access that verified site.
-
6
Confirm CMS Delivery coverage
Check that the saved Search Console property, GA4 web stream, and Bing site all cover the same public website in CMS Delivery. OLT rejects a conclusive mismatch and withholds dependent evidence when the website scope cannot be verified.
-
7
Start the initial sync
Saving the first valid property or site requests an initial sync for that connector. Connections reports whether it started; use Sync now when a saved selection says its sync did not start.
-
8
Read unavailable and warming-up states
Unavailable means OLT does not have usable provider evidence for that measurement. Warming up means a new connection has not returned usable rows yet and is not treated as a failure. Neither state is a measured zero or an estimated result.
GA4 website mismatch recovery
How to recover from a GA4 website mismatch
A GA4 website mismatch means OLT cannot verify that the selected property measures the canonical website configured in CMS Delivery. Follow this decision path before retrying a sync.
-
1
Verify the CMS Delivery website
Confirm that the public website in CMS Delivery is the canonical production website you intend to measure, including the correct host and path prefix.
-
2
Verify the GA4 web stream and production tag
Confirm that the selected GA4 property has a web stream for that website and that the production GA4 tag sends traffic from the CMS Delivery host to that stream.
-
3
If CMS Delivery is wrong, update it
Update the public website in CMS Delivery, save it, and then return to GA4 Connections to recheck website readiness.
-
4
If CMS Delivery is right, correct GA4
Choose the GA4 property whose web stream measures that website, or correct the selected property's web stream and production tag in Google Analytics before retrying.
What OLT preserves when it detects a mismatch
Rejected property selection
If OLT rejects a property selection because its web streams do not cover the CMS Delivery website, the saved property selection remains unchanged and no sync is queued.
Later host mismatch
If a later report window observes traffic only outside the CMS Delivery host, OLT retains prior Analytics evidence and withholds that unsuccessful window instead of marking it as a successful empty sync.
Provider comparison
Which SEO questions can each connector answer?
Use this source-based comparison to match each connector to its supported evidence. A listed capability does not promise that the selected property or site has returned a result.
Swipe or use the Left and Right Arrow keys to view all columns.
| Connector | Evidence question | Supported evidence |
|---|---|---|
| Google Search Console |
What Search Console evidence does OLT use? OLT stores organization-scoped Search Analytics evidence by page and by query plus page. Google can omit anonymized queries and truncate visible query rows, so named-query totals may cover only part of page demand. OLT withholds query-driven changes and verdicts when visible coverage is insufficient instead of treating omissions as zero or complete evidence. It can also surface URL Inspection indexing evidence for an eligible page and compare the connected CMS sitemap with the sitemaps Google has on file. |
|
| Google Analytics 4 |
What GA4 evidence does OLT use? OLT stores organization-scoped daily landing-page evidence for the verified website, including a separate Organic Search slice. It also reads an observational AI-assistant referral report by landing page and source. |
|
| Bing Webmaster Tools |
What Bing Webmaster evidence does OLT use? OLT stores organization-scoped Bing query and inbound-link snapshots for the connected site. It can also retain Bing URL information for selected pages and compare the canonical CMS sitemap with Bing's feed records. |
|
What Search Console evidence does OLT use?
OLT stores organization-scoped Search Analytics evidence by page and by query plus page. Google can omit anonymized queries and truncate visible query rows, so named-query totals may cover only part of page demand. OLT withholds query-driven changes and verdicts when visible coverage is insufficient instead of treating omissions as zero or complete evidence. It can also surface URL Inspection indexing evidence for an eligible page and compare the connected CMS sitemap with the sitemaps Google has on file.
- Page performance: Daily page rows preserve provider-reported clicks, impressions, CTR, and average position.
- Query performance: Daily query-and-page rows preserve the visible search terms Google reports, with clicks, impressions, CTR, and average position. Google can omit anonymized queries and truncate visible query rows, so named-query totals may cover only part of page demand. OLT withholds query-driven changes and verdicts when visible coverage is insufficient instead of treating omissions as zero or complete evidence.
- Indexing evidence: URL Inspection can return coverage, crawl, robots, fetch, canonical, rich-result, and index-verdict evidence for a page inside the selected property.
- Sitemap evidence: OLT compares the canonical CMS sitemap with Search Console's submitted sitemap records and retains a bounded submission receipt.
What GA4 evidence does OLT use?
OLT stores organization-scoped daily landing-page evidence for the verified website, including a separate Organic Search slice. It also reads an observational AI-assistant referral report by landing page and source.
- Validate the GA4 property: Connect Google Analytics 4, then choose the property with a web stream whose hostname matches the website in CMS Delivery. A matching GA4 web stream is necessary for property validation, but it is not sufficient for live traffic validation.
- Validate live GA4 traffic: The production GA4 tag must record sessions on the CMS Delivery hostname and within its configured path prefix. Conventional www and non-www hosts are equivalent; other subdomains and landing pages outside the prefix are excluded. If this check fails, verify the production tag and stream hostname, correct CMS Delivery when its website URL or path prefix is wrong, or select the property that measures the website.
- Organic landing pages: The Organic Search slice stores sessions and key events by date and landing-page path without mixing in all-traffic totals.
- AI-referral evidence: The observational report shows sessions, engaged sessions, key events, recognized assistant sources, and current-versus-previous trends by landing page.
What Bing Webmaster evidence does OLT use?
OLT stores organization-scoped Bing query and inbound-link snapshots for the connected site. It can also retain Bing URL information for selected pages and compare the canonical CMS sitemap with Bing's feed records.
- Query evidence: Bing's retained query-statistics window supplies weekly query rows with clicks, impressions, and average position.
- Link evidence: Inbound-link snapshots preserve Bing's reported link count for each returned page, while truncated responses cannot prove an omitted page has zero links.
- Indexing evidence: Bing URL information can report whether a selected URL is a page, its HTTP status, discovery date, and last crawl time, with failed reads kept unavailable.
- Sitemap evidence: OLT checks Bing's feed records for the canonical CMS sitemap and retains a bounded submission status.
What unavailable means
A missing connection, unreadable report, incomplete response, or unsupported metric stays visibly unavailable. OLT does not turn those gaps into estimated rankings, traffic, links, indexing, sitemap ingestion, or AI-referral totals, and this public page contains no organization data or connector secrets.