Google Search Console provides the data. The challenge is knowing where to look.
Google Search Console already provides a significant amount of information about how a website performs in search.
- Clicks
- Impressions
- CTR
- Average positions
- Queries
- Pages
- Countries
- Devices
The data is there.
But exporting it often produces several CSV files containing hundreds or thousands of rows.
At that point, the problem is no longer accessing the data.
The problem is turning it into something that can be examined quickly.
Raw data is useful, but structure matters
A Search Console export can answer many questions.
Which queries generate impressions but few clicks?
Which keywords are already close to the first positions?
Which pages receive visibility?
How has performance changed during the selected period?
Which countries and devices account for the traffic?
All of this information exists in the export.
But examining separate CSV files manually makes relationships between those metrics harder to see.
A useful analysis layer does not need to invent new data.
It needs to organize the existing data in a way that makes patterns and potential priorities easier to identify.
Building an analysis layer instead of another SEO score
This was the idea behind SEO Lens.
SEO Lens is a small browser-based tool I built to transform a Google Search Console ZIP export into a structured visual report.
The objective was deliberately limited.
It does not attempt to assign an arbitrary SEO score such as:
SEO score: 87/100
A single number would hide most of the information that actually deserves investigation.
Instead, the report keeps the underlying Search Console metrics visible and organizes them into several analytical views:
- performance overview
- performance evolution
- ranking distribution
- opportunities
- page performance
- countries and devices
- diagnostic
- SEO priorities
The goal is not to decide whether a website is "good" or "bad".
The goal is to make the available data easier to inspect.
Keeping the architecture simple
The processing pipeline is intentionally straightforward:
IMPORT
↓
PARSER
↓
NORMALIZATION
↓
ANALYSIS
↓
INSIGHTS / PRIORITIZATION
↓
RENDERING
The user exports data from Google Search Console as a ZIP file.
The ZIP is opened directly in the browser.
The CSV files are identified, parsed and normalized before the different analyses are calculated.
The resulting report is then rendered in the same page.
There is no backend involved in the analysis.
Handling different Search Console exports
One interesting implementation detail is that Search Console exports are not necessarily identical depending on language.
For example, a French export can contain files such as:
Graphique.csv
Requêtes.csv
Pages.csv
Pays.csv
Appareils.csv
Filtres.csv
The analyzer therefore needs a normalization layer.
Instead of making the analysis logic depend directly on a specific filename or language, aliases are used to identify equivalent datasets.
Once the files and columns have been normalized, the rest of the analysis can operate on a consistent internal structure.
This keeps localization concerns separate from analytical logic.
Finding opportunities without inventing information
The analysis is deterministic.
SEO Lens does not use AI to interpret the export.
For example, the tool can identify situations such as queries receiving significant impressions but relatively few clicks, or queries already ranking within ranges where further investigation may be useful.
The important distinction is that these are signals derived from the provided Search Console data.
They are not claims about the entire website.
A query with a low CTR may deserve investigation, but the export alone cannot explain why its CTR is low.
A page losing clicks may deserve attention, but Search Console data alone cannot diagnose every possible technical or content-related cause.
The tool can identify where to look.
It should not pretend to know what the data cannot establish.
Privacy as an architectural property
Another requirement was that importing Search Console data should not require sending it somewhere else.
SEO Lens therefore performs the analysis locally in the browser.
There is:
- no account
- no Google API connection
- no remote database
- no AI service
- no upload of the Search Console export to Palks Studio
The selected ZIP remains on the user's device while it is being processed.
This is not an additional privacy layer added around the application.
It is a consequence of the architecture itself.
If the server never needs the data, there is no reason to transmit it.
Why no direct Google Search Console API?
Connecting directly to the Search Console API could make importing data more convenient.
But it would also change the nature of the project.
OAuth, permissions, tokens, API configuration and server-side infrastructure would introduce additional dependencies and additional responsibilities.
For this use case, the existing Search Console export already contains the necessary input.
The workflow remains simple:
Google Search Console
↓
ZIP export
↓
SEO Lens
↓
Visual report
It requires one manual step, but removes several architectural ones.
That trade-off is intentional.
What the tool does not do
Defining the limits of an analysis tool is as important as defining its features.
SEO Lens does not perform:
- website crawling
- complete technical SEO audits
- backlink analysis
- HTML content analysis
- website modifications
- direct Search Console synchronization
It only analyzes the information contained in the Search Console export provided by the user.
The resulting report should therefore be considered a structured reading of Search Console data, not a complete SEO audit.
Small tools can solve narrow problems well
Not every technical problem requires a platform, an account system or a large application architecture.
Sometimes the useful part is simply the transformation between an existing input and a more understandable output.
In this case:
raw Search Console data
↓
structured information
↓
points worth investigating
The implementation can remain relatively small because the scope remains explicit.
There is no attempt to replace Search Console.
There is no attempt to automate every SEO decision.
The tool sits between the export and the person analyzing it.
SEO Lens
SEO Lens is available for free and runs directly in the browser.
No account is required and the Search Console export is processed locally.
The project also has a GitHub repository containing its technical presentation and documentation:
Top comments (2)
Nice Article!
Thanks. Glad you enjoyed the article and the approach behind SEO Lens.