Short answer
Check the public page response, crawl access, indexing rules, and canonical. Review the title, headings, useful content, and links. Check the page on a phone. Prioritize errors that prevent access or the reader’s task.
Before you start
Choose an important public page. Keep the reader's task beside you. Check access before spending time on titles or wording.
The list contains 15 checks. Some need Search Console or help from your site manager.
Access and indexing
- Check the response. The intended public page should return its content successfully. Investigate errors and unexpected redirects.
- Check crawl access. Read applicable robots.txt rules and firewall behavior.
- Check indexing rules. Look for unintended noindex directives. A robots.txt block and noindex have different effects.
- Check the canonical. Use consistent links and sitemap URLs. Confirm Google's selected version through URL Inspection.
A sitemap helps discovery. It does not guarantee indexing. Follow the indexing guide for a reported exclusion.
Titles and descriptions
- Write a specific title. Describe the page's subject in words the reader understands.
- Distinguish different pages. Similar titles can hide meaningful differences between services or locations.
- Write an accurate description. Summarize what the reader will find. Google may select page text instead.
There is no fixed character count that guarantees a complete search title. Display width and the selected wording can vary.
Content and structure
- Use a clear main heading. A single main H1 is a useful convention. Multiple H1s are not an automatic ranking penalty.
- Complete the reader's task. Add the facts, conditions, and evidence needed for the answer. There is no required word count.
- Check overlapping pages. Two URLs ranking for one keyword are not automatically harmful. Investigate pages serving the same task.
Use the writing guide when the page needs a better answer.
Links and media
- Check internal links. Repair broken destinations. Use link text that describes the destination.
- Match redirects to the move. Use a permanent redirect for a permanent move. Temporary redirects are valid for temporary moves.
- Describe useful images. Write appropriate alternative text for informative images. Decorative images can use empty alternative text.
Avoid changing an established URL only to make it shorter. A move also needs redirects and updated links.
Page experience
- Check the page on a phone. Read the content and complete the main action. Look for hidden text and difficult controls.
- Check loading and interaction. Review Core Web Vitals when field data exists. LCP measures loading, INP responsiveness, and CLS visual stability.
Lab tests help diagnosis. They are not the same as measurements from real visitors. A good score does not guarantee rankings.
Choose the first fix
Imagine a price page with a clear title but a blocked booking button. Fix the booking problem before polishing the introduction.
If the page has unintended noindex, investigate that first. If it is indexed but misses the question, improve the answer.
Record the change and date. Then check access, relevant exposure, and the intended customer action.
Use an audit as a starting point
The RankMySEO on-page audit finds issues in fetched HTML. Review its findings alongside Search Console and your own page checks.
An automated finding needs context. A short page, temporary redirect, or repeated keyword does not always need a change.
