Site Structure Analytics
Analyzing search traffic by the website's branch and folder structure: identifying growing sections and categories with declining traffic.
Updated: Dec 2025
What is Site Structure Analytics?
Instead of focusing on individual pages, this dashboard rolls search data up by the website's hierarchical folder structure (e.g. /news/ or /sport/) into a tree; every branch shows the combined stats of its subsections, so you can separate the sections driving organic growth from those that need attention.
Every number in the table carries a colored delta chip beside it, comparing that same metric against the preceding period of equal length — a fast way to see which part of the site is growing and which is declining, with no need to open a separate view.
What you see
- Page count — the number of unique pages that had clicks or impressions in the selected range, aggregated into the tree structure.
- Range selector — choose a time range (default: last 3 months) that both the table's figures and each number's comparison delta are calculated against.
- Tree table — Path column (chevron expands/collapses), Clicks, Impressions, CTR and Position; every number carries a colored delta chip comparing it against the preceding period of equal length — green for an improvement, red for a decline.
No separate detail panel; clicking the chevron at the start of each row expands or collapses its subsections and folders.
How it works
- Automatic tree configuration — the branch structure is categorized by page URL prefixes in Search Console reports; every new prefix (e.g. /shop/ or /en/) automatically forms its own branch in the tree.
- A folder's position — since a folder has no ranking of its own in Google, the position number shown for each branch is derived by combining the ranks of every page under that path.
- Period comparison — every delta beside a number compares that metric against the preceding period of equal length; if the last 3 months is selected, the comparison runs against the 3 months before that.
FAQ
The tree is built from the segments of your page address (URL Path). A site with a flat structure, or with addresses that carry no folders, therefore sees only a single-level list and cannot draw the full value from structural analysis. If your site has no folder scheme, we suggest you begin your analysis from the Search Results and Content Lifecycle dashboards.
No. The structure is formed only from the pages that drew an impression or a click in Google over the selected range. Pages that took no entry or impression from search in that window are not placed in the tree. This report is not a map of your whole site — it is a map of your real, live presence in search results.
A folder’s position is the weighted average rank of every page under that path. Pages with higher impressions are given greater weight, so the final rank fully reflects the real traffic performance of that branch. As in Google’s standard ranking, a smaller number indicates a better position.
The comparison always runs against the preceding period of equal length; if you selected the last three months, your figure is measured against the three months before that. The small chart beside each figure shows that same metric’s trend across the current range.
Yes. Every prefix in the URL structure creates its own branch of the tree. Paths such as /en/ or /fa/ are therefore grouped automatically as a separate section, and you can analyse the clicks, impressions and position of each language independently of the site as a whole. The same rule applies to prefixes such as /shop/ and to organisational sections.
The Search Console panel presents its page list under a limited row cap and shows part of the granular data in aggregated form. Shahin receives and rearranges the data directly through Google’s official API, under far higher caps and at the full path level. The difference therefore comes from how Search Console samples and caps its tables, not from a calculation error.
This report draws directly on Google Search Console. Because Google completes its final data with a two to three day delay, the end of your range will always sit a few days before today. The path structure and the tree sync continuously, but the metrics refresh at exactly the speed Google delivers them — a constraint shared by every tool connected to Search Console.
Was this page helpful?