Multi-location grader
For a brand with many locations or regional sites: every location page read together, its structured data, share tags, canonical and hreflang, graded on the eight things that only show across them.
/locations/Links every location page/locations/austin/LocalBusinessAddressHoursPhoneCanonical to itself/locations/dallas/LocalBusinessAddressHoursPhoneCanonical to itself/locations/houston/LocalBusinessAddressHoursPhoneCanonical to itself/sitemap.xmlLists every one of them
Each location has its own page with its own address, hours and phone, in its words and in its structured data, all linked from one hub.
What does it check?
Rules from the rulebook, and how many of the sites mttr has read miss each.
- Add structured dataAdd valid JSON-LD that says what the page is.61%of sites miss it
- Match structured data to the pageUse the schema type that matches the page: Article for guides, Service or Product for offers, Organization or WebSite for the home page.49%of sites miss it
- Set each page's canonical addressAdd a canonical link that points to the page itself.56%of sites miss it
- Set a share imageSet og:image so links to the page carry a picture.70%of sites miss it
Questions
Should each location have its own page?
Yes. A page for each location, with its own address, hours and phone in its words and in its structured data, is what a search engine or assistant can point to.
Which structured data suits a location page?
LocalBusiness, or its closest type such as Restaurant or Dentist, with the address, phone and opening hours of that location.
What is hreflang for?
For the same page in other languages or countries. It tells search engines which version to show where. A brand with one country and one language does not need it.
The whole site
One page is one part. A read checks every page against the whole rulebook and says what to fix first.
Read a whole site