Search Console

Set the app domain first, then open the SEO tab and connect Google. We match a Search Console property to that domain and store encrypted OAuth tokens.

If you connected before sitemap submit shipped, reconnect so we can write sitemaps.

1. Performance — daily clicks, impressions, CTR, and position (web search, ~28 days). Search Console daily totals lag about two days. Google’s last-24-hours report is delayed several hours; EventDash does not inherit that wait for on-site visits.
2. Needs attention — EventDash pages with traffic that Search Console shows as not indexed or with zero impressions. Those EventDash pageviews update through the current hour.
3. Recommendations — ranked opportunities from your on-site events, your Search Console property, and live HTML on up to 50 priority URLs (homepage, top traffic, top impressions, index gaps, then sitemap fill). Each card cites the numbers used. Thin content is flagged when sampled HTML is under 150 visible words and the URL already has search impressions, or the page is already high-traffic. Contact and private paths are skipped. This is not a full-site crawl. Search Console daily totals still lag about two days. URL Inspection is sampled (up to 25 URLs).
4. Page × query — Search Console rows for a URL plus the query. That is how we score two of your pages competing for one query, and titles that do not cover the query you already rank for (synonyms count; EventDash does not invent titles). The SEO tab also lists query landings with EventDash views and goals on that URL. Those goals are events on the landing page. Search Console does not tell us which query produced a goal. Ahrefs cannot see which of those URLs converts in your funnel.
5. Country and device — Search Console totals for the same window, shown under search performance after a sync. They are not split by landing page and they do not change recommendation scores.
6. Money-page weighting — converting URLs (goal events, or search clicks with no goal) score higher for the same thin title, duplicate, or canonical issue than a blog.
7. Indexing — priority pages, with Check indexing. That preflights the URL, resubmits the sitemap Search Console already has, and re-inspects around 24 hours, day 5, and day 14. Inspection is a sample. Google decides what is indexed.
8. Request indexing — still a manual click in Search Console. There is no API for that button.
9. AI search — whether robots.txt allows ChatGPT, Claude, Gemini (Google-Extended), Perplexity, and Copilot on /, plus visits whose referrer host is one of those products. Google-Extended is not Google AI Overviews. AI Overview and AI Mode impressions are included in the Search Console web totals. They are not these visits and not crawler hits. The Search Analytics API does not return that report as its own series, so the panel charts it only when Google returns a generative search appearance. Zero visits is common because many AI answers send no referrer. This is not a citation score and not an indexation report. Refresh works from an app domain before Search Console is connected.
10. Sitemap — submit or resubmit /sitemap.xml for the connected property. A URL that already converts, or that already earns impressions or visits, is flagged when the live sitemap leaves it out.
11. Change markers — pin a note on a day, or connect GitHub (Standard and Professional) to overlay default-branch commits and releases on the Performance chart and the Overview activity timeline. Search Console daily totals still lag about two days, so a Tuesday ship often shows up in Wednesday–Friday totals. EventDash does not claim a commit caused a ranking move.