Wide dawn photo of a brass spotting telescope on a tripod at a stone balcony, looking out over layered teal hills as the sun rises in orange, for setting up Google Search Console for WordPress.

هذا المقال متوفر باللغة العربية — اقرأ بالعربية

If you own a WordPress site in Egypt, Saudi Arabia or the Gulf, setting up Google Search Console for WordPress is the cheapest SEO step you can take. It’s free, it comes straight from Google, and it answers questions no plugin can answer on its own: which searches show your pages, which pages Google indexed, and what is stopping the rest. This guide walks you through the setup, the verification options, the sitemap, and the reports worth opening every week, with notes for Arabic and bilingual sites.

I’ll keep it practical. Everything here comes from Google’s own Search Console Help pages and the WordPress documentation, linked at the end, so you can check any step yourself.

What Google Search Console for WordPress does (and what it doesn’t)

Search Console is Google’s tool for site owners. It shows how your site appears in Google Search, lets you tell Google about your sitemap, and reports indexing and page experience problems. It doesn’t change your rankings by itself, and adding your site doesn’t make Google rank it higher. Think of it as the dashboard, not the engine.

It’s also different from Google Analytics. Analytics tells you what visitors do after they land on your site. Search Console tells you what happened before the click: the searches, the impressions, your average position and the click-through rate. You want both, but if you only have time for one this month, Search Console gives you the SEO picture.

  • Performance: clicks, impressions, CTR and average position, grouped by query, page, country, device and date.
  • URL Inspection: Google’s indexed version of a single page, a live test, and the option to request indexing.
  • Page indexing: which of your pages Google indexed and why some were left out.
  • Sitemaps: where you submit your sitemap and see any errors Google found while reading it.

Step 1: choose the right property type

Search Console calls each site you add a property. For a website you get two choices, and picking the right one saves you trouble later.

Property type What it covers How to verify
Domain All subdomains (www, m and so on) and both http and https DNS record only
URL prefix Only URLs that start with the exact prefix, including the protocol Several methods (file, tag, Analytics, Tag Manager, DNS)

My usual advice: add a Domain property for the whole site, because it catches every version of your URLs in one place. If your site has separate language folders like /en/ and /ar/, also add a URL prefix property for each folder. That way you can read Arabic and English data separately without filtering every time. Google’s help pages say themselves that a URL prefix property is the way to limit data by path segment, like example.com/en/.

One detail people miss: a URL prefix property for http://example.com/ does not include https://example.com/ or the www version. If you go with URL prefix only, add the exact version your site actually uses.

Step 2: verify that you own the site

Before Google shows you any data, you have to prove ownership. Google lists several methods, and the verification screen shows which ones are available for your property.

The DNS method (needed for a Domain property)

You add a TXT record that Google gives you at your domain provider or at your DNS host, such as Cloudflare. It’s the only way to verify a Domain property. It can take a while for the record to appear, so if verification fails right away, wait and try again rather than adding duplicate records.

The HTML tag method

Google gives you a meta tag to place in the head of your homepage. On WordPress you rarely need to edit theme files for this. Most SEO plugins have a field for the Google verification code, and Site Kit by Google can handle verification for you. If you do edit a theme, use a child theme, or the tag disappears with the next theme update.

The HTML file method

You download a small file from Google and upload it to the root of your site with your host’s file manager or SFTP. It works well, but some managed hosts restrict root access, so check before you start.

Google Analytics or Tag Manager

If your site already runs a Google Analytics tracking code or a Google Tag Manager snippet that you can access, Search Console can verify you through it. This is quick, but there’s a catch Google mentions: if someone later changes the template and the code disappears, verification can fail.

That’s why Google suggests adding more than one verification method. Search Console checks your token from time to time, and if it can’t find it, you get a warning and later lose access after a grace period. On WordPress, a theme switch or a cleanup plugin can remove a tag without anyone noticing, so a second method (DNS is the most stable) is cheap insurance.

Step 3: connect WordPress the easy way with Site Kit

If you’d rather not copy tags and records by hand, Site Kit by Google is the official plugin from Google. According to its WordPress.org page it has more than 5 million active installs, and at the time of writing its latest version is 1.189.0, requiring WordPress 5.2 and PHP 7.4 or later. It connects Search Console, Analytics and other Google services, and shows key numbers inside your WordPress dashboard.

It’s a good option for owners who want a quick summary without logging into Google every day. Two things to keep in mind:

  • The dashboard view is a summary. For deep work like comparing date ranges or checking indexing reasons, you still open Search Console itself.
  • Every plugin adds code to maintain. If you already verified with DNS and only need the data, you don’t have to install it.

Step 4: submit your WordPress sitemap

A sitemap is a file that tells Google which pages on your site it should know about. Since WordPress 5.5, core creates a basic XML sitemap at /wp-sitemap.xml. If you run an SEO plugin such as SEOPress, Yoast or Rank Math, it usually replaces the core sitemap with its own, at a different address. Check the sitemap settings in your SEO plugin and open the URL in a browser before you submit it.

  1. Open Search Console and pick your property.
  2. Go to Sitemaps in the left menu.
  3. Type the sitemap path (for example sitemap_index.xml or wp-sitemap.xml) and click Submit.
  4. Come back after a few days and check the status and the number of discovered URLs.

Google notes that you must have owner permissions to submit a sitemap in this report. If you don’t, you can list the sitemap in your robots.txt file instead. A typical line looks like this:

Sitemap: https://example.com/sitemap_index.xml

Google also says a small site (about 500 pages or fewer) where every page is reachable through links from the homepage may not need a sitemap at all. Most WordPress sites have one anyway, and submitting it costs nothing, so I still do it for every client.

Step 5: read the Performance report

This is where most of the value is. By default the report shows clicks and impressions for the past three months. You can switch metrics and dimensions:

  • Clicks: how many times people clicked through to your site from Google Search.
  • Impressions: how many times your site appeared in results.
  • CTR: clicks divided by impressions.
  • Average position: the average position of your topmost result.

A simple routine that works for small business sites:

  1. Open the Queries tab and sort by impressions. Look for searches with many impressions but few clicks. These pages already rank; a clearer title and meta description can often lift the click rate.
  2. Open the Pages tab and find pages that lost clicks compared with the previous period. Check whether the content is out of date or a newer competitor page took the spot.
  3. Open the Countries tab. If you sell in Saudi Arabia but most impressions come from elsewhere, your content may not match what your real customers search for.
  4. Open the Devices tab. In our region most traffic is mobile, so a page that does well on desktop but poorly on mobile deserves a look at its speed and layout.

Google also notes that traffic from AI Overviews is counted inside the regular web search numbers in this report. We covered that in our guide to getting Arabic pages cited in Google’s AI answers.

Step 6: use URL Inspection for single pages

When you publish an important page, or fix one, paste its full URL into the inspection bar at the top of Search Console. You’ll see whether the page is in Google’s index, which canonical URL Google picked, and whether the page can be indexed. The live test checks the current version of the page, and the Request indexing button asks Google to crawl it.

Use Request indexing for a handful of key pages, not as a daily habit for every post. Google’s recrawl guidance says there’s a quota for individual requests, and for many URLs the sitemap is the better route. Requesting a crawl also doesn’t guarantee the page gets indexed quickly.

Step 7: check Page indexing without panicking

The Page indexing report lists indexed and not indexed pages with a reason for each group. New owners often see a long list of not indexed URLs and assume something is broken. Usually it isn’t. Google itself says it’s fine for a URL not to be indexed for the right reasons, such as a noindex tag, a duplicate URL or a deleted page that returns 404.

On WordPress, the usual suspects in the not indexed list are:

  • Tag and author archives that your SEO plugin set to noindex on purpose.
  • URLs with parameters, such as ?replytocom= or sorting options in WooCommerce.
  • Old pages you deleted without a redirect.
  • Attachment pages, if your SEO plugin doesn’t redirect them.

What deserves attention is an important page, like a service page or a top product, sitting in the not indexed group. Inspect it with URL Inspection and fix the cause. Google also says that for sites with fewer than 500 pages you may not need this report much; a site: search and URL Inspection on key pages are often enough.

Tips for Arabic and bilingual WordPress sites

Arabic sites have a few extra things to watch in Search Console:

  • Separate folders, separate properties. As mentioned above, URL prefix properties for /ar/ and /en/ make the data easier to read.
  • Arabic URLs look encoded. If you use Arabic slugs, Search Console may show them percent encoded. That’s normal. Many sites use English slugs for both languages to keep URLs short and easy to share.
  • Queries come in both scripts. People in the region search in Arabic, in English, and in Arabic words typed in Latin letters. Check the Queries tab for all three before you decide which keyword a page should target.
  • Hreflang is still on you. Search Console no longer has an International Targeting report, so you check language tags with a crawler or an SEO plugin. Our article on SEO for sites in Arabic and English explains the setup.

A weekly 15 minute routine

When What to check Why
Weekly Performance: clicks and impressions versus last period Spot drops early
Weekly New queries with high impressions Find title and content ideas
Monthly Page indexing for key pages Catch pages that fell out of the index
After changes URL Inspection and Sitemaps status Confirm Google sees the update

Speed problems also show up here through the Core Web Vitals report. If your mobile pages are flagged, our walkthrough on making Arabic WordPress pages load faster is a good next read.

Common mistakes to avoid

  • Verifying the wrong version. Adding http:// when the site runs on https://, or the non www version when you redirect to www. A Domain property avoids this.
  • Relying on one fragile method. A verification tag inside a theme you later replace. Add DNS as a backup.
  • Submitting the wrong sitemap. Submitting wp-sitemap.xml when your SEO plugin disabled it. Open the URL first and make sure it loads.
  • Giving full access to everyone. Search Console lets owners add users with full or restricted permission. Give agencies and freelancers only what they need, and remove them when the job ends.
  • Checking once and forgetting. The data is only useful if someone reads it regularly.

Frequently asked questions

Is Google Search Console free?

Yes. Search Console is a free Google service. You only need a Google account and access to your site or your domain’s DNS to verify ownership.

How long until I see data?

Google says data collection starts as soon as someone adds the property, even before verification, but it takes a few days for data to start showing up. A brand new site may need longer before it appears in search at all.

Do I need Site Kit to use Search Console with WordPress?

No. You can verify through DNS, an HTML tag, a file, or your SEO plugin, and use Search Console directly in the browser. Site Kit is convenient if you want summaries inside WordPress, but it’s optional.

Can I give my developer access without sharing my Google password?

Yes. As an owner you can add users to the property from its settings, with full or restricted permission, so nobody needs your password.

Wrapping up

Setting up Search Console takes less than an hour, and the payoff lasts for as long as your site is online: you stop guessing about SEO and start reading what Google actually sees. Verify with a stable method, submit the right sitemap, and give the Performance report fifteen minutes a week.

If you’d like us to set it up and watch it for you as part of ongoing care, take a look at our SiteCare maintenance plans, or book a free consultation and we’ll go through your reports together.

References