Skip to main content
Site Audit

Site audit breakdown

Updated over 5 months ago

Initial configuration

Text box

  • Users can enter a URL and the Site Audit tools, also known as the brute force crawler, will crawl all the pages under the domain and give technical metrics for site health, indexable and non indexable pages, tech specifics and how to fix them and more.

User Agent

  • Users can choose the agent they want to do the crawling with. We suggest Search Atlas’s own agent.

Pages to Crawl

  • User can select how many pages to crawl at once, it is set up to crawl the first 100 pages, but if a domain exceeds that the number can be adjusted.

Crawl Speed

  • Users can select how long they want the crawler to spend time analyzing the website. It is set up to 20 pages per second. The more time spent crawling the more granular the data could be.

Crawl frequency

  • The time period that the software will update the data, with a re-crawl. It is set up to re-crawl every 7 days but users can adjust that to their preferences.

“Overview” Tab

Users can:

  • Scope Button: Get a summary of the analysis done.

  • Export to Google Docs.

  • Share Audit: via URL.

  • Connect GSC and GA: to enrich the data with Google’s insight’s.

  • Recrawl Site: To self heal the dashboard and also to get a more updated Analysis.

Site health

  • Site Health score: Measured out of 1000 points. 1000 being the most optimal result. This is a metric to help the user understand their score and how to improve the technicals of a website. Anything above 800 is acceptable.

  • Total Pages of a website.

  • Total Issues found on the website crawled.

  • Site Health changes: It’s a graphic way to check if the score of the site health is improving or worsening over time.

  • All page changes: you can track when improvements are done, also track what pages were added, changed, redirected or removed.

  • Total issue changes: track how many of the issues found have been addressed.

  • All Page types: Check the status of the page in the code.

  • Site Indexability: Track what pages are indexable and what pages are not.

  • Chrome User Experience Report: The Chrome User Experience Report (CrUX) provides user experience metrics for how real-world Chrome users experience data on millions of websites.

Top 10% Important Pages

  • Same data points previously mentioned but just focused on the top 10 pages selected based on Pagerank.

Page Explorer

Top buttons

  • Create segment: this allows the user to filter and divide the data however they prefer. Add new column filters from within the table, sort columns and include a certain amount of pages on their segments.

  • Share Audit: via URL.

  • GSC/GA: connect both Google integrations to enrich the data.

  • Export: as an xls file.

  • Manage Columns: Select and reorder the columns you want to see.

Page Explorer Insights

  • Page: The exact URL of the page analyzed.

  • Depth: Page depth is a metric that measures how many clicks it takes for a user to get from the home page to the next page on the site.

  • Type: A page type in Compose is a content type which defines a custom field structure for a web page or any other composition of content. Some typical examples for page types are “Landing page”, “Homepage”, “Product page” or “Blog post”.

  • Importance: With the previous metrics we give the user an estimate of how important a page is, the closer it is to the home page the more important it tends to be

  • Page Health: An estimate of how healthy that page is from 0 to 1000. Depends on the amount of issues found in that specific page.

  • HTTPS: Hypertext transfer protocol secure (HTTPS) is the secure version of HTTP, which is the primary protocol used to send data between a web browser and a website.

  • Status: What’s the code status of the page, 200 tends to signify a stable page. Status like 400 or 500 tend to signify issues.

  • Title: Here the user can find the exact title given to the page.

  • Meta Description: A meta description tag generally informs and interests users with a short, relevant summary of what a particular page is about. They are like a pitch that convince the user that the page is exactly what they're looking for.

  • H1: Here the user can find the exact H1 present on the page.

  • Indexable: This is the metric that shows that due to the amount of issues present in a page, whether that makes the page indexable or not.

  • In XML Sitemap: Whether the page in question is present in the site map of the domain.

  • Incoming Internal Links: Internal links are hyperlinks that point to different pages on the same website. These differ from external links, which link to pages on other websites.

  • HREFLANG: is an HTML attribute used to specify the language and geographical targeting of a webpage. If you have multiple versions of the same page in different languages, you can use the hreflang tag to tell search engines like Google about these variations. This helps them to serve the correct version to their users.

  • Schema Org Types: Schema.org is defined as two hierarchies: one for textual property values, and one for the things that they describe. This is the main schema.org hierarchy: a collection of types (or "classes"), each of which has one or more parent types.

  • View button: When clicked it takes the user to the page insights where they can analyze specific pages and see all the issues that affect them.

Domain Level

  • Here users can check all the issues that are affecting the domain in general, a great way to keep track of the issues on a general level perspective.

Did this answer your question?