Upload a CSV file with your search traffic data and receive a detailed branded vs non-branded breakdown with actionable insights
FAQ
Is my data secure when I use this tool?
Yes, your data is completely secure. All processing happens locally in your browser – your CSV file never leaves your computer. We don’t use any server-side processing, don’t store your data, and don’t transmit it anywhere. The tool runs entirely in your browser as JavaScript.
Do you store my Search Console data?
No, we don’t store your data. Once you close this page or refresh it, your data is completely gone. For convenience, we only save your brand term configuration preferences in your browser’s local storage so you don’t have to re-enter them each time you visit.
What format should my CSV file be in?
Your CSV file should contain the following columns from Google Search Console: query, page, clicks, impressions, ctr, and position. You can export this data directly from the Performance section of Google Search Console. The file size should be under 10MB for optimal performance.
How do I define my brand terms?
In the configuration section, enter all variations of your brand name separated by commas. For example, if your brand is “Acme,” you might enter: “acme, acme inc, acmecorp”. For more complex brand detection, you can enable the custom regex option and define your own pattern.
How does the tool identify branded vs. non-branded traffic?
The tool uses your specified brand terms to categorize each search query. Any query containing one of your brand terms is classified as “branded,” while all others are “non-branded.” If you enable custom regex, you can create more sophisticated matching patterns. You can also toggle case sensitivity depending on your needs.
How accurate is the language detection feature?
The language detection feature identifies language codes in URL paths (like /en/, /es/, /de/) based on a comprehensive list of common language codes. While this works well for sites with standard language path structures, it may not detect all custom implementations. You can disable this feature if your site uses a different multilingual structure.
What insights will I get from the analysis?
The tool provides multiple analysis views: Overall summary (Results), URL path analysis, language breakdown, individual query analysis, data quality assessment, and actionable insights. You’ll see metrics like clicks, impressions, CTR, and average position broken down by branded vs. non-branded segments, along with visualizations and recommended actions.
What does the Data Quality tab show?
The Data Quality tab evaluates your data for issues like missing values, statistical outliers, duplicates, and inconsistencies. It provides an overall health score and specific recommendations for improving data quality. This helps ensure your analysis is based on reliable data and identifies potential problems that might affect your results.
Will the tool work with large datasets?
The tool is optimized for datasets up to 10MB in size. For larger files, you may experience slower performance since all processing happens in your browser. If you have a very large dataset, consider filtering your Search Console export to focus on a specific date range or subset of queries before uploading.
Can I export the analysis results?
Yes, you can export your analysis results. Each tab includes export buttons that allow you to download the data as CSV files. You can export URL analysis data, branded queries, non-branded queries, language analysis, and insights. You can also download a PDF summary of your results or export all data at once.
What browsers are supported?
The tool works with all modern browsers, including Chrome, Firefox, Safari, and Edge. Since it uses modern JavaScript features, older browsers may not be fully supported. For the best experience, use the latest version of your preferred browser.
What if I encounter an error during analysis?
If you encounter an error, check that your CSV file contains all required columns and is properly formatted. The tool performs validation checks and will display specific error messages if issues are detected. If problems persist, try using a smaller dataset or ensure your browser is up to date. All errors are handled locally and no error logs are sent to any server.