Welcome
What WebRankPage measures, and where to start reading.
WebRankPage reads a web page the way a search engine does and tells you what is worth changing, in the order worth changing it. This documentation covers what it measures, how to read what it gives you back, and how to run the whole thing from code.
What it actually does
You give it a URL. It fetches that page from your server, exactly as a visitor or a crawler would, and reads the HTML that came back. Then it runs every check it knows about, groups the results, scores them, and puts the things that matter most at the top.
Three things about that are worth knowing before anything else, because they explain most of what you will see.
| We read what your server sends | Not what a browser builds afterwards. Search engines index the HTML that arrives, so that is what we audit. A page whose content is assembled by JavaScript can be analysed with rendering turned on, but the default is the document itself. |
| We measure pixels, not characters | Search results truncate on rendered width. A title of "Illinois" and one of "llllllll" are the same number of characters and nowhere near the same width, so a character count cannot tell you whether yours will be cut. |
| Every number says where it came from | Core Web Vitals can be real-user field data or a synthetic lab run. Those are different claims about different things, so each reading is labelled rather than blended into one figure. |
Where to start
| If you want to | Read |
|---|---|
| Analyse your first page | Your first report |
| Know what the score is made of | Scores and grades |
| Understand a finding you were shown | Findings |
| Watch pages over time | Tracked pages |
| Audit a whole site | Site crawl |
| Do any of it from code | API overview |
How this is organised
Reading a report is the reference for what you are looking at: every number on the page, and every check, with what triggers it and what to do. It is the section to search when a finding says something you do not recognise.
The dashboard covers the things beyond a single page: watching a URL over time, crawling a whole site, monitoring for downtime, and working with a team.
API is the reference for doing all of it from code, with samples in six languages.
Search is the fastest way through this. It matches the text of every section, not just the titles, so pasting a phrase from your report usually lands on the check that produced it. Press / anywhere in the docs.