CONNECT GOOGLE SEARCH CONSOLE TO MUSE
Set up Google Search Console reporting in Muse
Adzviser retrieves the source data through its MCP reporting tools. Muse uses those results to answer your questions. Connect the source in Adzviser, then authorize Muse to use that connection.
Connect Google Search Console in Adzviser
In Adzviser, sign in to Google Search Console and allow Adzviser to read its reporting data. Add the source to the workspace you want to use in Muse.
Open Adzviser setup →Authorize Adzviser in Muse
Open Muse.ai and send: “Can you connect to custom Adzviser MCP at https://mcp.adzviser.com/http?” Select Connect on the Adzviser card, sign in to Adzviser, and select Complete Authorization via MCP. Return to Muse.
https://mcp.adzviser.com/httpVerify the first result
Ask Muse to list your Adzviser workspaces and their sources. Choose the workspace and confirm the property. Request a small report for a known period before expanding the analysis.
The Adzviser reporting connection is read-only. It can retrieve data for analysis; it cannot edit source records or campaigns.
A USEFUL FIRST GOOGLE SEARCH CONSOLE REPORT
Build a query-to-page review of lost clicks
Build a report you can check
Compare the last 28 complete days with the preceding 28 days for one Search Console property. First rank queries by absolute clicks lost, showing impressions, CTR and position for both periods. Then request landing-page detail for the leading queries. Preserve the same search filters throughout so the comparison measures a real change in the selected traffic.
Separate a visibility change from a CTR change
Fewer impressions with similar CTR calls for a different investigation from stable impressions with falling CTR. Average position is an aggregate, not a fixed ranking for every search. Query tables can omit anonymized searches and other rows, so their sum may not equal the property total.
Choose the pages to inspect first
Ask Muse to group the affected pages into visibility losses and CTR losses. For each group, request a review action and the evidence behind it. Check the actual search result and page content before changing a title; the report alone does not reveal every competing result or search intent.
Metrics for this report: Clicks; Impressions; CTR; Position.
Relevant breakdowns: Search query; Landing page.
These are starting fields, not a promise that every combination belongs in one report. Use separate requests for different reporting levels and check the full field catalog for additional coverage.
COPY INTO MUSE
Run your first Google Search Console analysis
Paste this after connecting. Change the period or research subject to match your question, and let Muse confirm the selection before retrieving results.
Use Adzviser to analyze Google Search Console. List my workspaces and ask which connected property to use. Compare the last 28 complete days with the preceding 28 days for one Search Console property. First rank queries by absolute clicks lost, showing impressions, CTR and position for both periods. Then request landing-page detail for the leading queries. Preserve the same search filters throughout so the comparison measures a real change in the selected traffic. Use these metrics in compatible reports: Clicks, Impressions, CTR, Position. Relevant breakdowns: Search query, Landing page. Check field compatibility and use separate tables for different reporting levels. State the actual reporting dates or observation window. Show the supporting rows, then give a short conclusion and one next investigation. Label missing data and separate observed changes from possible explanations.
