inemaSEO 7 — Systems: build your own open Semrush|INEMA.CLUB-PRO

Lesson 3 · 16 min

agente-ready: a 0–100 score with weights you can change

"AI readiness" scanners give you a score, but almost none publish how it is calculated. agente-ready keeps each weight, the reason, and the source in a versioned file, pesos.json. You get your site's score, see what weighs most, and if you disagree with a weight, you change it and run again.

Start the lesson
An inspector with a clipboard checks a list in front of the door of a commercial building.

In this lesson you will

  1. 1The 6 categories and the weight of each criterion
  2. 2How the score is calculated (and what leaves the denominator)
  3. 3Why llms.txt weighs 2 and WebMCP is preparation
  4. 4Run with your own weights

Goal: get your site's readiness score and change one weight in pesos.json to see the score change.

01How the score comes out

Weights add up to 100. Tap each step.

Click each block in the diagram to see what it does.

A score with the math in the open: you can disagree with a number and show why.

02The criteria that weigh the most

Tap each group.

1. Access

robots.txt lets search bots (12) and user-requested agents (6) in; the CDN does not block the User-Agent of OAI-SearchBot, PerplexityBot, and Perplexity-User (12).

If a bot can't read the page, nothing else matters to it.

03Get the score and change a weight

Run it from the ferramentas/agente-ready folder.

Terminal · your site's score
cd ferramentas/agente-ready
python3 agente-ready.py https://yoursite.com --saida nota/yoursite
Terminal · your weights
cp pesos.json my-weights.json
# open my-weights.json and change the "peso" of one criterion (e.g.: webmcp_api from 5 to 0)
python3 agente-ready.py https://yoursite.com --pesos my-weights.json --saida nota/yoursite-my-weights
Why I changed the weight (template)
# Weights for <yoursite.com> — <dd/mm/yyyy>
criterion: <criterion id>
original weight: <n>  →  my weight: <n>
reason: <e.g.: my audience doesn't use browser agents; WebMCP is a draft with no stable browser>
score with pesos.json: <n>  ·  score with my weights: <n>
Example from the repository
www.inema.club: nota 93/100 (5 páginas, 22 requisições).
  [falha, peso 2] Link para Sobre ou Contato na home: sem link /sobre, /about ou /contato

eventos.inema.pro: nota 69/100 (5 páginas, 15 requisições).
  [falha, peso 8] Organization ou Person com @id no JSON-LD da home: 0 entidade(s); com @id: 0
  [falha, peso 5] Autoria identificada: 0 de 5 com autor (meta, rel=author ou JSON-LD)
  [falha, peso 5] Data de publicação ou atualização: 0 de 5 com data (JSON-LD, meta article ou <time>)
  [falha, peso 5] Ferramentas WebMCP registradas com document.modelContext.registerTool(): nenhum registerTool() em 2 script(s) de mesma origem + inline

04Practice: the score and your weight

In lesson 7 the score joins the monthly routine.

E1 · The score

15 min

Run agente-ready on your site and write down the score and the 3 failing criteria with the highest weight.

Done when: you have the score, the 3 criteria with the weight of each, and the evidence the report shows.

E2 · Disagree with a reason

15 min

Copy pesos.json, change one weight with a written reason, and run again with --pesos.

Done when: the "why I changed the weight" template is filled in with both scores, and they are different.

05Test what you learned

The explanation shows up after your answer.

Question 1 of 4

Your site has no form. What happens to the 4 points for forms?skill

06Takeaways

Open mathWeights, reason and source in pesos.json; whatever doesn't apply is left out of the denominator.
What weighs mostBot access (30) and extractable content (26) come before everything else.
2026 yardstickllms.txt is optional (weight 2); WebMCP is preparation, not ranking.

Going further

Previous lessonNext lesson