Skip to main content

Google Search Console

Which account, and the direct URL​

Sign in with the Axxya account, not a personal one

The property is owned by cawood@axxya.com. A personal Google account such as cawood@gmail.com is not a user on the property and gets "Oops, you don't have access to this property". This is an account problem, not a permissions bug in Search Console.

The property is https://nutritionistpro.com/, registered as a URL-prefix property rather than a domain property.

Direct link to the page indexing report:

https://search.google.com/u/1/search-console/index?resource_id=https%3A%2F%2Fnutritionistpro.com%2F

The /u/1/ segment selects the second signed-in Google account in the browser session, so it only lands on the right account if the accounts are in that order. When it redirects to /u/0/ and reports no access, force the account explicitly with the authuser parameter instead, which is reliable regardless of ordering:

https://search.google.com/search-console/index?resource_id=https%3A%2F%2Fnutritionistpro.com%2F&authuser=cawood@axxya.com

Drilldown pages for each exclusion reason use the same URL with /index/drilldown and an item_key parameter.

Reading the page indexing report​

Most of the "not indexed" count is expected behavior and should not be treated as a fault list. As of the July 2026 review, 374 pages were indexed and 326 were not, and only two of the 326 were genuine problems.

What is normal and should be ignored:

  • Excluded by 'noindex' tag: WordPress /feed/ URLs, AIOVG /player-embed/ URLs, and the ?s={search_term_string} placeholder that comes from the site's schema markup. None of these should ever be indexed.
  • /1000 suffixed URLs and truncated URLs such as /nutr, /best-, /he. These are legacy or scraped links that appear nowhere in the current site HTML. WordPress fuzzy-matching already redirects them to the right page.
  • Tag, category, author, and video archive pages, and their /feed/ variants. Standard WordPress output.
  • wp-admin/admin-ajax.php 403s, which come from the AIOVG plugin.
  • Alternate page with proper canonical tag, which means canonicalization is working as designed.

What is worth investigating:

  • Real, sitemap-submitted content pages appearing under "Crawled - currently not indexed". Cross-check the not-indexed list against the sitemap URLs, because that intersection is the only part that matters.
  • 404s for pages that once existed, for example retired /client/<name>/ pages. Redirect them if they had inbound links.

"Crawled - currently not indexed" on a page that returns 200, carries a self-referencing canonical, and has no noindex is Google's editorial judgment, usually that the page is too similar to other content on the site. It is not a technical fault, and requesting indexing without changing the content will not alter the outcome.

How long changes take​

Three different timescales, and confusing them leads to premature conclusions:

  • Sitemap fetch and parse: minutes to a few hours. The Sitemaps page status changes to "Success" with a discovered URL count. This only confirms Google read the file.
  • Recrawling the URLs: days to weeks. A sitemap submission is a hint, not an instruction.
  • The page indexing report updating: the slowest. It is built from batch processing and lags noticeably. Check the "Last update" date shown on the report; during the July 2026 review it was roughly two and a half weeks behind the current date.

Resubmitting a sitemap repeatedly does not speed anything up. Submit once and wait.

For immediate feedback on a single page, use URL Inspection > Test Live URL, which queries Google in real time instead of showing cached report data. "Request Indexing" on the same screen has a quota of about ten per day.

After a sitemap or URL change​

Resubmit https://nutritionistpro.com/sitemap_index.xml under Indexing > Sitemaps once the verification steps in WordPress configuration pass.

AI crawler settings are not an indexing factor​

Cloudflare's AI bot controls and the Google-Extended directive govern AI training and Gemini only. They have no effect on Google Search indexing, and Googlebot has never been blocked on this site. Rule this out early rather than investigating it. See Cloudflare.