How-to
Fix your site for AI answers with a coding agent
A fix report is a handful of files: an llms.txt, an FAQ, a comparison page, descriptions, and a list of changes. Putting each one in the right place is the part people put off. Every report download now includes one more file, AGENT-BRIEF.md, that turns all of it into a task list a coding agent can follow.
What is in the brief
One ordered list. Each task says where the file goes, includes the content inline, and ends with a check the agent can run, such as fetching /llms.txt and confirming it is served as plain text. Anything that has to happen on another site, like claiming a review listing, is kept in a separate section marked as a job for a person, so the agent does not try to edit your codebase to do it.
How to use it
- Download your report from the dashboard and unzip it.
- Open your site’s repository in Claude Code, Cursor, Codex or any other coding agent.
- Give it the file: “Read AGENT-BRIEF.md and do the tasks in order.”
- Review the changes before you merge. The brief tells the agent to use only the facts in it.
The brief works with any agent because it is a plain markdown file. No account or connection is needed. To check your score from the agent itself, see connecting your coding agent to meraGEO.
Then check that it worked
Publishing the files does not change what an assistant says on the same day. Models pick up a site on their own schedule. Monitoring scans your domain every week and records what changed on your site, so you can see your mentions before and after.
Start with a free scan
See where ChatGPT, Claude and Gemini name you and where they skip you, then decide what to fix.
Run a free scanRelated: how to write an llms.txt.