Guides2 min readUpdated
Fix what fails first
Work down the fix list one rule at a time: see which pages fail it, fix them, read the site again, and check the rule now passes.
Which fix should I make first?
The one at the top of the report. Fixes are ranked by how much their rule weighs and how many pages fail it, so the first moves the score most, and a rule that keeps crawlers out always comes first. Make it, publish, and read the site again to check it now passes.
Steps
Open the report
The report leads with the fix worth the most. Every failing rule is listed under it, ordered by how much the rule weighs and how many pages fail it, so the first one moves the score most. A rule that closes the site to crawlers always comes first.
See the pages behind one rule
Each fix names pages that fail it, says what the rule found, and says what to do in the rulebook’s words. In the app, a rule opens every page that fails it.
Fix it and publish
Change the pages on your site and publish them. A fix to a shared template often fixes every page at once.
Read it again
Press Read it again on the report. A site is read at most once every 10 minutes; asked sooner, mttr says when it may be asked again.
Check what changed
When the read is done, the report shows the new score. In the app, History shows each rule now passing, each rule newly failing, and every page it changed on, as it was and as it is.
A fix’s place in the list is its rule’s weight times the share of the site’s pages that fail it. A heavy rule failing on a few pages can sit below a lighter one failing on most.
Where a model was asked and could not be relied on, the finding waits for a person and does not count against the page. See Needs a person.
With an agent
An agent works the same list in a loop: mttr_brief for the fixes, a change in the site’s own repository, mttr_rescan to read it again, mttr_job until the read is done, and mttr_changes to see which rules now pass. On a site set to approve, it sends each change to you with mttr_propose first, and deploys only once you approve it.
From the command line or the API
mttr rescan example.com --why "added sources to the guides"curl -X POST https://mttr.si/api/v1/sites/example.com/rescan \
-H "Authorization: Bearer $MTTR_KEY" \
-d '{ "reason": "added sources to the guides" }'If something is not right
| What you see | Why it happens | What to do |
|---|---|---|
| The rule still fails after the fix | The page is not published yet, a cached copy was read, or a second page on the same template still fails | Open the page in a private window, then look at what the rule found this time |
| The read stopped at the limit | mttr reads at most 100 pages of a site, so a page you fixed may not have been read | The report says when a read stopped early. Link the page from one that is read |
| The score went down | A template change can fix one rule on every page and break another | History lists every rule that newly fails, and the pages it fails on |