--- title: "Gemini SEO" description: "Gemini SEO from ShoutRank. Google’s chat product, tracked separately from AI Overviews and from classic rankings." canonical: https://shoutrank.com/gemini-seo markdown: https://shoutrank.com/gemini-seo.md --- # Gemini SEO Gemini SEO from ShoutRank. Google’s chat product, tracked separately from AI Overviews and from classic rankings. Gemini SEO is about Google’s chat product: what it says when someone asks there, and which sources it shows. Gemini sits inside Google’s product family and still answers as a chat. Teams fold it into the AI Overview report because both say Google on the tin. The queries, the replies, and the sources diverge. ShoutRank gives Gemini its own column in [GEO](https://shoutrank.com/geo). The overview stays on the [AIO](https://shoutrank.com/aio) page. If a check did not include Gemini, the report says that. ShoutRank does not guarantee a ranking or a citation. ## The problem ### The overview cites you and Gemini does not. Or the reverse. A single “Google AI” metric hides the one that matters to the buyer you have. ### The reply uses an old name. A rebrand or a product split never made it into the pages Gemini can retrieve. The chat continues the old story. ### Account-specific replies get treated as the public answer. A signed-in test with your own history is not what a new buyer sees. We say which kind of check was run. ## How ShoutRank approaches it We define the prompt set and whether the check is signed out. We store the reply and any sources Gemini shows. We do not average it with the overview. Page fixes follow [LLM optimization](https://shoutrank.com/llm-optimization): a definition, a limit, and a source a person can open. ## What the work includes ### Gemini prompt log The questions, the date, and whether the session was clean. ### Naming check Product names, old brands, and features the reply still invents. ### Source list URLs Gemini showed, if it showed any. ### Split from AIO A written line in the report so the two Google surfaces are not merged later. ## Process ### Discovery Agree the prompts and the session rules before the first test. ### Audit Run them and store replies. Note when no source is shown. ### Strategy Compare names and claims to the current site. ### Implementation Correct your pages first. Third-party corrections only where the publisher has a reason to care. ### Monitoring Repeat under the same session rules. ### Optimization Investigate prompts that diverged from the overview, instead of averaging them away. ### Reporting Two tables: Gemini, and a pointer to the overview log rather than a copy of it. ## Why ShoutRank ### We refuse the blend Gemini and AI Overview stay in different documents even when the client uses one phrase for both. ### Session rules are part of the method A check that used a logged-in account is labeled. It is not presented as the default buyer view. ### Old names are bugs If the reply uses a retired brand, that is a finding, not a mention to celebrate. ## How success is measured Prompts that name the current brand in Gemini. Prompts that link a URL you assigned. Claims that contradict the live site. A named client result is published when that client clears the figure. Until then the report is the measurement. ## Questions ### If we rank in Google, will Gemini follow? Often the sources overlap. Often they do not. We read Gemini instead of inferring it from rankings. ### Do you optimize for Gemini’s model card or for the product? For the product a buyer can open. We do not claim access to unpublished model weights or a private tuning deal. ### Is Copilot included here? No. Copilot is a different product. It can be added to a GEO brief. It is not silently folded into Gemini. ## Related - [AIO](https://shoutrank.com/aio): The other Google surface, kept separate. - [GEO](https://shoutrank.com/geo): Where Gemini sits with the other chat products. - [Claude SEO](https://shoutrank.com/claude-seo): A different chat product, on its own log.