Content integrations

The Finish setup checklist on Content → My Content shows whether the selected project has four useful information sources. These connections add context to recommendations and make it easier to investigate the path from a content idea to a published and cited page. They are not all prerequisites for creating an article.

The checklist is scoped to the selected project. A Google account can be connected without a property yet being assigned to that project, so the checklist may ask you to select a property after you sign in.

Google Search Console

Search Console contributes Google search queries and page performance. It can help identify a page with many impressions but few clicks and prioritize an article using real search queries. It answers questions about Google search visibility and clicks; it does not report what AI answers cite.

Select Connect Search Console to authorize a Google account. After it returns to PromptEye, choose the Search Console property that matches the project. If the account is already connected, the checklist opens the property selector rather than repeating account authorization. The connection is marked complete when a property is bound to the project.

If a property is missing, confirm that the signed-in Google account has access to it and that you are selecting the property for the right website. If account authorization works but the property is not assigned to the project, open the selector from the checklist and complete that step. For property and connection troubleshooting, see Google Search Console and Analytics.

Google Analytics 4

GA4 helps measure what visitors do after arriving on your content. It can add context about engagement and conversions so you can compare visibility signals with site activity. Analytics measures visits and events according to the GA4 property configuration; it does not explain which answer cited an article.

Choose Connect GA4 to authorize a Google account, then select the correct GA4 property for the current project. If a Google connection already exists, use the property selector. The setup checklist marks GA4 complete when the project has a bound property.

Do not expect GA4 totals to match Content citations, AI bot requests, or Search Console clicks. A citation is an answer-source event; a crawler request is an automated fetch; Search Console records Google search performance; GA4 records analytics sessions and events according to its own rules. These are different measures.

Server logs and AI crawler tracking

The server logs checklist item helps PromptEye see which AI crawlers fetch website pages. This can reveal whether bots reach a page or repeatedly fail to fetch it. It is marked complete when the project has a tracking setup or recorded traffic events.

The checklist action opens Traffic → Overview. Follow that area’s setup instructions to install the website tracking code and review the data it records. A connected Google account does not install the website tracker. For request fields, bot identification, errors, and setup steps, see Traffic settings and setup.

Use these logs as crawl evidence. They do not show every human visitor, every unknown bot, or how often a brand appears in AI answers. A crawler visit is a signal that a bot fetched a page, not proof the page was included as a citation.

Sitemap

A sitemap gives PromptEye a list of the project’s published URLs. Comparing the list with crawl activity helps identify coverage gaps and pages AI crawlers may not reach. Adding a sitemap does not guarantee that all listed URLs are live, crawled, indexed, or cited.

Choose Add sitemap to open the sitemap and SEO crawler area. Add or manage the sitemap there, and use the coverage view to inspect URL-level information and synchronization status. The Content checklist marks the item complete when a sitemap configuration is present. That means setup exists; it is not a claim that every URL is healthy.

What the checklist status means

A completed connection indicates that the project is linked or the setup is done. It does not certify that the source has complete data, is current, or contains every signal you need. If the report using a source looks empty, check that the correct account, property, project, tracker, or sitemap is in use and that the source has had time to record data.

The four setup items are independent. You can connect Search Console without GA4, install traffic tracking without adding a sitemap, or use article generation while some connections are incomplete. Recommendations can only use the context available to the project, so missing source data may change which ideas appear or how confidently you can investigate them.

Dismiss setup reminders

Dismiss an incomplete checklist item if you do not want to work on it now. The dismissal is remembered in this browser for the selected project. It hides the reminder in that browser; it does not disconnect the account, remove the sitemap, uninstall traffic tracking, or delete collected data. Dismissal does not necessarily follow you to another browser or device.

A completed item is no longer shown as an incomplete task. If you later need to review a connection, open its related integration or Traffic settings page. If you dismissed an item by mistake, the current checklist does not offer a visible undo action; visit the relevant setup area directly.

Project access and setup actions

People with read-only project access can view the Content page and setup status, but the checklist disables incomplete setup actions. Ask a project owner or editor to authorize Google, choose properties, or make project changes. This is separate from viewing recommendations or opening existing articles.

For Google connections, an authorization step and project property selection are separate. For server logs and sitemap, the action opens the corresponding Traffic setup area. Follow the instructions on that screen; the Content checklist itself does not install a tracker or edit your sitemap.

Which source should I check?

• If you want to know which Google queries show your pages, check Search Console.
• If you want to know what people do after landing on an article, check GA4.
• If you want to know whether AI crawlers fetch a URL, check server logs / Traffic.
• If you want to compare the site URL inventory with discovered crawl activity, check sitemap coverage.
• If you want to know whether an AI answer cited a page, check Citations and the article’s citation count in the library.

These sources complement one another; their counts will not necessarily match. For example, a page can be cited without a fresh bot fetch in the selected log period, a crawler can fetch a page without it being cited, and an analytics session can occur without any citation event recorded.

Common questions

Do I need to finish all four integrations?

No. They provide different kinds of context, and article creation does not require every checklist item. Connect the source that supports the question you are investigating.

Why does Search Console say connected but the checklist still asks me to select a property?

The Google account can be authorized before a specific Search Console property is bound to the selected project. Choose the property for the project’s website to finish setup.

Does adding a sitemap index all the pages?

No. A sitemap supplies a URL list. Crawling and indexing are separate processes, and a URL in a sitemap is not guaranteed to be indexed.

Does server logging show citations?

No. It shows automated requests from recognized crawlers. Citation reports inspect AI answers and show when your page is used as a source.

What does dismissing an integration reminder do?

It hides that incomplete reminder in the current browser for the selected project. It does not disconnect or delete the underlying integration or data.