Search Console in 15 Minutes: The Five Reports That Matter

Most business owners open Google Search Console once, see a wall of charts, and close the tab. The tool is free, it comes straight from Google, and it is the only place that shows how Google itself sees your website: which searches show your pages, which pages Google refuses to index, and whether your site is slow for real visitors. The problem is not a lack of data. The problem is that nobody has told you which five screens matter and what a healthy reading looks like.

This guide is a fifteen-minute routine built around five reports. It is written for owners and marketing managers of service, tourism, hospitality and real estate websites, but the technical notes are precise enough for your developer to act on. Everything about how the reports behave comes from Google’s own Search Console documentation, which we read again before writing this post. Where a statement is engineering judgment rather than documentation, we say so.

Before the Fifteen Minutes: Set the Property Up Correctly

The routine only works if the data is complete, so one setup decision matters more than any report: the type of property. Search Console offers a Domain property and a URL-prefix property. A Domain property covers every protocol and subdomain of your domain (http, https, www, non-www, and any subdomain) in one view, and it is verified through a DNS record. A URL-prefix property covers only the exact address you enter, including the protocol, so https://www.example.com/ and https://example.com/ are separate properties with separate data.

For a business site, we recommend the Domain property as the main view, because it removes the most common blind spot: traffic and errors that sit on a host variant you forgot about. If your site was ever moved between www and non-www, or from HTTP to HTTPS, a URL-prefix property for the old variant may be the only place the old URLs still show up. Our migration checklist explains why you should keep every variant verified for months after a move.

Two practical points before you start. First, Search Console does not back-fill data from before verification, so verify the property today even if you are not ready to read it. Second, give access to the people who need it, and no more: the owner role can change settings and submit requests, while a restricted user can read reports. Keep at least two verified owners so that losing one person’s Google account never locks the company out of its own search data.

Minutes 0 to 5: The Performance Report

The Performance report for Search results is the report that answers the commercial question: are people finding us, for what, and are they clicking? According to Google’s official Search Console Performance report documentation, the report shows how search traffic changes over time, which queries bring visitors to your site, and which pages generate the highest and lowest click-through rates.

It reports four core metrics. Clicks are the times a user clicked through to your site from Google Search. Impressions are the times your site appeared in results. CTR is clicks divided by impressions. Average position shows the average ranking position associated with your search result data.

The default view covers the last three months, and the table underneath the chart can be switched between Queries, Pages, Countries, Devices, Search appearance and Dates. The report also lets you filter by search type, including Web, Image, Video and News. Make sure the search type is the one you intend before you draw conclusions, because an image-heavy tourism site can have a very different picture in Image search than in Web.

Pass One: Branded Versus Non-Branded Queries

Open the Queries tab and filter out your brand name. A new filter with the option Queries not containing and your company name, in both Latin and Arabic spellings, shows how much of your search visibility depends on people who already know you. A site where nearly all clicks come from the brand name is not yet working as an acquisition channel. It is working as a directory listing. The goal of an SEO programme is to grow the non-branded line.

If you operate in more than one language, remember that the same brand can be typed in several spellings. Add each variant to the exclusion, otherwise your non-branded line will quietly include branded searches.

Pass Two: Queries Close to the First Page

Sort the Queries table by impressions and look at rows with an average position between roughly 8 and 20. These are searches where Google already considers your page relevant but ranks it where few people click. They are usually the cheapest improvements on the site: a clearer title, a stronger opening paragraph, a section that answers the question directly, and two or three internal links from related pages. This is judgment from experience rather than a rule in the documentation, but the logic is simple. A page at position 12 for a query with real demand needs a modest push. A page at position 70 needs a different page.

Pass Three: High Impressions, Low CTR

Now look for rows with many impressions and a click-through rate far below your site’s average. Two causes dominate. Either the title and description do not match what the searcher wanted, or a result type above you, such as a map pack, an answer box or a travel module, is taking attention. Compare against your own pages rather than against a published benchmark: CTR varies enormously by query type, device and position, and an external average tells you very little about your market.

Pass Four: Country and Device

Switch the table to Countries and then to Devices. For an Egyptian business that sells internationally, this view often contains the most valuable surprise. A Red Sea hotel may find that a meaningful share of impressions comes from Germany, Poland or the Czech Republic while the site has no page written for those readers. A real estate developer may find the opposite: strong impressions abroad and almost none from Cairo. The Devices tab shows whether your audience is mostly on mobile, which should shape every design and speed decision. If you run a bilingual site, add a Pages filter containing /ar/ to see the Arabic section on its own, and compare it with the English section. Our guide to multilingual SEO for Red Sea tourism sites covers how to act on the differences.

Reading the Numbers Honestly

Three details prevent wrong conclusions. The newest days are preliminary: Search Console draws them as a dotted line, and they can change within hours, so never judge a campaign by yesterday. The chart and the table can show different totals, because the chart aggregates by property while the Pages and Search appearance tables aggregate by page. And the position you see in Search Console is not the position you see when you search yourself: results vary by time, location, device and search history, so personal checks are anecdotes, not measurements.

When you want to compare periods, use the date comparison control and compare like with like: the same number of days, ideally with the same weekdays included, and the same season where your business is seasonal. A hotel comparing October with November without adjusting for the tourist season is measuring the calendar, not the website.

Minutes 5 to 8: The Page Indexing Report

If the Performance report shows what Google sends you, the Page indexing report shows what Google has accepted. Every URL Google knows about is either Indexed or Not indexed, and for the Not indexed group the report gives a reason and a source, which tells you whether the cause sits on your website or with Google. Only the website-side issues are normally yours to fix.

Do not panic at a long Not indexed list. Many of the reasons are normal and correct. What matters is whether the pages you want to rank are in the Indexed group, and whether the reasons attached to your important pages make sense. These are the reasons you will meet most often:

• Crawled, currently not indexed. Google fetched the page and has not indexed it yet. It may be indexed later, and resubmitting is not needed. If many important pages sit here for weeks, the usual cause is content that looks thin, duplicated or low value to Google, and the fix is improving the page, not requesting indexing again.
• Discovered, currently not indexed. Google knows the URL but has not crawled it, often because it postponed crawling to avoid overloading the server. A large count here on a small site is worth a look at server speed and at how many low-value URLs you are generating.
• Excluded by noindex. The page tells Google not to index it. Correct for thank-you pages and internal search results. A serious problem if it appears on a service page, and a classic leftover from a staging site that went live with the setting still on.
• Page with redirect. A URL that redirects elsewhere. Only the target can be indexed, so this is normal for old addresses after a redesign.
• Duplicate without user-selected canonical. Google decided the page duplicates another and chose a different canonical. This is not an error in itself, but check the pair with URL Inspection to confirm that Google picked the version you want.
• Soft 404. The page says “not found” but returns a normal success status. Return a real 404 for missing pages, or add real content to pages that are wrongly flagged.
• Not found (404). Acceptable for pages you removed on purpose. If the content moved, a permanent redirect to the new address is the right answer.
• Blocked by robots.txt. Googlebot cannot crawl the page. Note that this does not reliably keep a page out of the index if other pages link to it. To keep a page out, allow crawling and use a noindex directive.

Use the sitemap filter at the top of the report, because it changes the question from “what does Google know about” to “what did we ask Google to index, and what happened to it”. Select your submitted sitemap and read the Not indexed reasons for only those URLs. Anything in your own sitemap that is not indexed deserves an explanation. If a page is in the sitemap and carries a noindex tag, your site is sending Google contradictory instructions.

When you fix an issue across all affected pages, use Validate fix. Google first checks a sample of the affected URLs and stops if the problem is still there; otherwise it rechecks the known affected URLs. Validation can take up to about two weeks, so do not repeat the request while a cycle is running. An issue stays listed for 90 days after its last instance disappears, so a count of zero is the real sign that it is resolved.

For a single page, the URL Inspection tool at the top of Search Console is the companion to this report. It shows whether a specific URL is indexed, which canonical Google selected, and what Googlebot saw on a live test. When a client says “my new page is not on Google”, this is the first place to look, before anyone blames the content.

Minutes 8 to 10: The Sitemaps Report

The Sitemaps report is short, and that is why it is easy to neglect. It lets you submit a sitemap, shows the status of each submitted file, and shows how many page URLs Google parsed from it. The statuses are Success, Has errors and Couldn’t fetch. Success means the file was fetched and read without errors. Has errors means some problems occurred, though the URLs that could be parsed are still queued. Couldn’t fetch means Google could not retrieve the file at all, which usually points to a blocked path, a server error or a wrong address.

Two points are frequently misunderstood. The discovered pages count is the number of URLs parsed from the file, and it is not a promise of crawling or indexing. Use the Page indexing report, filtered by that sitemap, to see what actually happened. And deleting a sitemap from the report does not make Google forget it or its URLs.

The limits are worth knowing if your site is large, for example a hotel group with thousands of room pages or a marketplace: a single sitemap can hold up to 50,000 URLs or 50 MB uncompressed, and a sitemap index file can list up to 50,000 sitemaps. A sitemap index can list sitemap files only, not other index files, and its entries must be full URLs.

What to check in these two minutes: that the sitemap index your CMS produces is the one submitted, that its status is Success, that the discovered count is plausible for the number of pages you actually have, and that the list does not include URLs you have deliberately noindexed or redirected. On WordPress sites, an SEO plugin usually generates the index automatically, and the common faults are old sitemap URLs from a previous plugin still being submitted, or a staging domain accidentally submitted. Google also notes that a small site, roughly 500 pages or fewer and fully linked from the homepage, may not need a sitemap at all, so do not treat a missing sitemap as an emergency on a brochure site.

Minutes 10 to 13: Core Web Vitals

The Core Web Vitals report shows how real visitors experience your pages, using field data from the Chrome UX Report. This is a different thing from the lab score you get when you run a speed test from your own laptop. It measures three metrics. Largest Contentful Paint (LCP) measures loading and is Good at 2.5 seconds or less. Interaction to Next Paint (INP) measures responsiveness and is Good at 200 milliseconds or less. Cumulative Layout Shift (CLS) measures visual stability and is Good at 0.1 or less. The thresholds for Poor are above 4 seconds for LCP, above 500 milliseconds for INP and above 0.25 for CLS.

Three behaviours of the report matter in practice. Results are reported separately for mobile and desktop, so a site can be Good on desktop and Poor on mobile, and mobile is where most tourism and local-service traffic arrives. Each group of similar URLs takes the status of its worst metric, so one poor metric makes the whole group Poor. And groups with too little data are left out: a new property, or a low-traffic page type, may show “No data available” even though the pages are fine. The absence of a warning is not the same as a pass.

When a group is flagged, the report lists example URLs. Treat them as examples of a template, not as individual pages to fix one by one. On most WordPress and Laravel sites, a Poor status points to a template-level cause: a large hero image served without a preload hint, a slider that shifts the layout after load, a heavy third-party script, or a slow server response on uncached pages. Fix the template and the whole group improves. After the fix goes live, use Start Tracking: Search Console then monitors for 28 days, and the issue counts as fixed if no affected URLs appear in that window. Because the data is a rolling field measurement, expect the improvement to appear gradually rather than the day you deploy.

This report tells you that a problem exists, not why. For the diagnosis and the order of fixes, see our page speed optimisation approach, and our comparison of hosting in Egypt or abroad if server response time is the weak point.

Minutes 13 to 15: Manual Actions and Security Issues

The last two minutes go to the two reports you hope are empty. A manual action is a notice that a Google reviewer found pages on your site violating spam policies. Affected pages can rank lower or disappear from results, often with no visible sign to your visitors, which is why a notice can go unseen for months if nobody looks. The notice appears in the Manual actions report and in the Search Console message center. If one appears, fix the issue on all affected URL patterns, check them with URL Inspection, and then use Request Review, explaining the problem, the steps taken and the result. Reviews can take days or weeks, and you should not resubmit before receiving a decision.

The Security issues report flags signs that the site was hacked or behaves in ways that could harm visitors, such as phishing or installing unwanted software. Affected pages may carry a warning label in search results, and browsers may show a warning page before visitors reach the site. The impact on trust and enquiries can be immediate. If this report is not empty, follow the response order in our guide on what to do in the first 60 minutes after a hack, then clean the site and verify the fix before asking for a recheck.

Set up email notifications for the property owners so that these two reports reach a person without anyone opening the dashboard. Make sure the address belongs to a mailbox somebody actually reads, not to a former employee or an agency that no longer manages the site.

Reading Search Console for a Bilingual or Multi-Language Site

Search Console has no dedicated language report, so you build the view yourself with filters. Use the Pages filter with the path of each language folder, for example /ar/ for Arabic, and compare clicks, impressions and average position between the language sections. Use the Countries tab to see where each language is read. Three patterns to look for:

• An English page that earns impressions in Egypt while its Arabic equivalent earns almost none. The Arabic page may be missing, thin or not indexed, and the Page indexing report will usually say why.
• Arabic queries where the first-page result is a different dialect from the one your page uses. Formal and Egyptian Arabic behave like different keyword sets, so check what searchers actually typed in the Queries table before rewriting.
• Impressions from a country with no page in that language. This is a market signal. Decide whether it is worth a translated page before building anything.

Search Console does not validate your hreflang annotations in a dedicated report today, so verify them with a crawler or by inspecting the page source, and use the Pages and Countries views to confirm the result: if the right language version ranks in the right country, the annotations are doing their job.

The Fifteen-Minute Routine on One Page

Run this once a week for the first month, then every two weeks. The sequence matters because each step uses the previous one as context.

• Minutes 0 to 5, Performance: last 28 days compared with the previous 28 days. Note the change in clicks and impressions. Check branded versus non-branded. Pick one query near position 8 to 20 and one page with low CTR to improve this week.
• Minutes 5 to 8, Page indexing: look at the indexed total trend and at any new Not indexed reasons. Filter to the submitted sitemap. Investigate any important page that is excluded.
• Minutes 8 to 10, Sitemaps: confirm Success status and a plausible discovered count.
• Minutes 10 to 13, Core Web Vitals: mobile first. Note any group that moved from Good to a worse status after a deployment.
• Minutes 13 to 15, Manual actions and Security issues: both should be empty. Check that notifications reach a real mailbox.

Keep a short change log next to it: the date of each redesign, plugin update, migration or content push. When a line moves in Search Console, the explanation is almost always an event on that list. Without the log, you will spend your fifteen minutes guessing.

What to Do With What You Find

Reading the reports is only the first half of the job. Turn each finding into one concrete task with an owner and a date. A fast mapping works as follows. A drop in clicks across the whole site after a release points to a technical cause, so check Page indexing and robots.txt first. A drop on one page group points to a template or content change. Rising impressions with flat clicks point to titles, snippets or ranking position. A rising count of Discovered but not indexed URLs points to crawl efficiency: too many near-duplicate URLs from filters, tags or tracking parameters, or a server too slow for Google to crawl comfortably.

Keep your expectations realistic about timing. Changes to titles and content can show up in the Performance report within days or weeks, depending on how often Google crawls the page, while indexing validations take up to two weeks and Core Web Vitals tracking takes 28 days. Make one change at a time where you can, so you can attribute the result, and resist reacting to a single day of data.

Finally, remember that Search Console describes Google Search only. It says nothing about visitors from other search engines, social media, ads or direct visits, and it does not measure bookings, calls or enquiries. Pair it with an analytics property that tracks the actions that make you money, and connect the two views in a monthly report. A hotel owner should be able to read one page and see impressions, clicks, direct booking requests and WhatsApp conversations side by side.

One technical caution on data retention: the Performance report only keeps a limited history, widely documented as about sixteen months. If you want year-on-year comparisons for a seasonal tourism business, set up a scheduled export of Search Console data to BigQuery now. The export only collects data from the day it is switched on, so every month you wait is a month of history you will never be able to compare against.