SEO & content · USE CASE

Why is my website not showing up on Google? Find the cause for each page.

A page that isn’t on Google has one of five problems: Google hasn’t indexed it, something technical blocks it, the content is thin or out of date, it shows for a different search, or it ranks too low to be seen. PageOptimized, Search Console and WordPress together tell you which one, post by post, and your assistant makes the fixes you approve.

Data sources
Assistant
Destination
Try it with your data Free with up to 3 data sources · No credit card
EXAMPLE WEBSITE

Why is my website not showing up on Google?

CausePostsWhat fixes it
Not indexed8Content and links
Technical problem4WordPress and SEO plugin
Past position 404Links, not rewrites

Search Console Aug 21–Nov 18, 2026 · Audit Nov 16 · Inspected Nov 18

Of 48 published posts, 22 aren’t found on Google for the search they were written for. 8 aren’t indexed at all, 4 have a technical problem, 3 are thin or out of date, 3 show up for a different search, and 4 are indexed and matched but sit past position 40, where a rewrite won’t help. The other 26 are indexed and show up in the top 40 for their search.

WHERE THE RESULT GOES

WordPress

Apply the change, then check the updated record.

Example use case

Ask. Follow up.
Take the next step.

✦ AI assistantSample use case
PageOptimizedSearch ConsoleWordPress
YOU

  1. 01
    3 crawled, not indexed · 3 discovered, not crawled · 2 unknown to GoogleFix the content or the links

    Next

  2. 02
    noindex · canonical elsewhere · Google picked another post · broken linksTwo fixes in WordPress, two in your SEO plugin

    Next

  3. 03
    Minimum wage · predictive scheduling · split shiftRefresh the post

    Next

  4. 04
    Indexed, but no impressions for the intended queryRetitle for the search you want

    Next

  5. 05
    No audit problems · current · matched to the queryLinks, not rewrites

    Next

Search Console Aug 21–Nov 18, 2026 · Audit Nov 16 · Inspected Nov 18

01 · CONNECT YOUR DATA

Your tools. One place to ask.

3 of 3 Free data sources
No credit card · Daily refresh

DatapipeYour project
Your AI assistantor a report in Sheets / Data Studio
  1. Create your free workspace

    Sign up with your company email. Your first project opens on Data sources.

  2. Add the data sources

    Choose the accounts for this website. Authorize access and select the property or site.

  3. Bring your question

    Connect your project to a supported AI assistant, or build your source reports.

Create a free account →
Setup steps & what you need

Email/password signups confirm their email first. Use Google signup with a company account if you prefer.

  • PageOptimized: Create an API key on the API keys page in PageOptimized, paste it in Data sources, then click Save and check. Reading audits and search data is free; a key with write access is needed only for changes such as work items or a new audit. Setup guide ↗
  • Search Console: Authorize Search Console with Google and select the property you can access. Setup guide ↗
  • WordPress: Enter your site URL, WordPress username, and a dedicated Application Password. Setup guide ↗

Free includes 3 data sources across the workspace. One account/property added to one project counts as one. Extra properties or the same account in another project use another slot.

02 · ASK A USEFUL QUESTION

Start with a prompt.
Follow the evidence.

Copy these in order into your connected assistant.
Each builds on the answer before it.

01

Find the posts that aren’t showing up

Read the full prompt
Use only this Datapipe project’s authorized data. Discover the connected accounts, datasets and compatible fields first. Confirm dates, timezones, currencies and data coverage. Keep missing or unmatched rows visible; never substitute sample data. Compare the sources explicitly and explain every match. Do not change source records or send messages.

Read the latest completed PageOptimized audit for this site: Audit crawled pages with Page URL, HTTP status code, Canonical URL, Word count, Internal links, Indexable, In sitemap and Crawl depth, and Audit issues with Page URL, Issue type and Severity. Read Search Console clicks, impressions and position by page for the last 90 days, and by page and query for the same days. Read WordPress posts with Post ID, Title (raw), Status, URL, Publication date (GMT) and Modified (GMT), and keep the published posts. Match the three on the normalized URL (lowercase host, no query string or fragment, with or without the trailing slash) and tell me how many posts have no impressions at all, how many have impressions, and which posts are missing from the audit or from Search Console.
02

Inspect the evidence for each post

Read the full prompt
Run URL Inspection on every published post with no impressions, up to 100 URLs, and return Index verdict, Index coverage state, Indexing allowed, Page fetch state, Last crawl time, Google canonical URL and Declared canonical URL. Remember this is Google’s indexed version, not a live test. For each post with impressions, list its queries with impressions and position. I will give you the query each post was written for; where I haven’t, infer it from the title and slug and mark it as inferred. Show which posts get no impressions for their own query, and the position of that query where they do. Don’t treat a missing Search Console row as zero search demand: Google leaves out rare queries.
03

Find the cause and propose the fixes

Read the full prompt
Put each post in exactly one bucket, checking in this order: technical (noindex, canonical pointing elsewhere, Google canonical different from the post, page fetch errors, broken internal links), not indexed (crawled or discovered and not indexed, or unknown to Google), thin or out of date (under 600 words or not modified in 12 months), shows for a different search (impressions, but none for its own query), past position 40 for its own query, or fine. Show the evidence for each. Then propose the changes: new titles, SEO titles and meta descriptions, the exact text to replace for broken links, internal links from posts that rank, and refreshed passages where I confirm the facts. Show each change before you make it and wait for my approval. Then make the approved changes in WordPress, add a PageOptimized work item for each post that needs links from other sites, and tell me what stays with me, such as noindex and canonical settings in the SEO plugin and requesting indexing in Search Console.

03 · USE WHAT YOU FIND

Put each post in one bucket, then fix it.

  1. 01

    Read the audit, the search data and the posts.

  2. 02

    Inspect the posts Google isn’t showing.

  3. 03

    Put each post in one bucket, then fix it.

Make the change

The assistant proposes each change with the exact text it removes and adds. You approve it, Datapipe makes it and records it in the change history: who made it, when, and the values before and after. A change waits in Datapipe for a second approval only when the data source or the person is set to need one.

  • Replace text in a postwordpress.post.replace

    Fixes the 3 broken links in the labor cost percentage post, adds a sentence with a link from 2 ranking posts to each of the 4 posts Google hasn’t reached, and swaps the outdated passages in the minimum wage and predictive scheduling posts once your team confirms the figures.

  • Update a postwordpress.post.update

    Retitles the break laws post and the shift swap policy template, rewrites their openings so they stop repeating their neighbours, and expands the thin split shift post.

  • Change a post’s SEO title or meta descriptionwordpress.post.seo

    Gives the 3 posts that show for a different search an SEO title and meta description built on the query you want. Needs Yoast SEO or Rank Math and the free Datapipe SEO fields plugin.

  • Add a work item to the projectpageoptimized.work_item.create

    Opens one link outreach item per post stuck past position 40, with the page, the query and an owner, in your PageOptimized work queue.

  • Submit a list of page URLsbing-webmaster.url.batch

    If Bing Webmaster Tools is also in the project, submits the changed posts to Bing, up to 100 URLs at a time. Bing confirms it received them, not that it will crawl them.

  • Submit an approved sitemapsearch-console.sitemap.submit

    Resubmits your sitemap once the orphan post is in it. Search Console accepting it confirms the request, not crawling or indexing.

  • Start a site auditpageoptimized.audit.run

    Starts a fresh crawl after the fixes to confirm the broken links and duplicate title are gone. It uses PageOptimized credits, so you set the page limit.

Stays with your team. Removing the noindex and correcting the canonical are settings in your SEO plugin. Requesting indexing in Search Console, redirects when you fold one post into another, confirming new legal and wage figures, and link outreach to other sites stay with your team.

Check the result at your next review.

Two weeks after the fixes, inspect the 11 posts that had no impressions again; most should have moved to Submitted and indexed or at least Crawled. 28 days after each post’s new modified date, compare its Search Console impressions and the position of its own query with the 28 days before. Run a new PageOptimized audit to confirm the 3 broken links and the duplicate title are gone. Don’t expect the 4 posts past position 40 to move within a month; check them again after the outreach work items are done.

Implementation tips for this use case

Check causes in order, because an earlier one hides the later ones. Not indexed or technical comes from URL Inspection and the audit: a noindex, a canonical pointing elsewhere or Google choosing another URL is technical; crawled or discovered and not indexed is not indexed. Then broken internal links. Then thin (under 600 words) or out of date (not edited in 12 months). Then whether the post gets any impressions for the query it was written for, and if it does, whether that query sits past position 40. The assistant proposes the fix for each post, you approve it, and Datapipe makes it in WordPress and records it in the change history.

WHEN YOU NEED MORE CONTEXT

Go a little deeper.

The method and reporting checks
behind this example.

How to find out why a page isn’t showing up on Google
  1. Read the audit, the search data and the posts.

    Add your PageOptimized project, your Search Console property and your WordPress site to one Datapipe project. From PageOptimized, read Site audits to find the latest completed audit, then Audit crawled pages (Page URL, HTTP status code, Canonical URL, Word count, Internal links, Indexable, In sitemap, Crawl depth) and Audit issues (Page URL, Issue type, Severity) for that audit. From Search Console, read clicks, impressions and position by page, then by page and query, for the last 90 days; Google reports those dates in Pacific time and leaves out rare queries. From WordPress, read WordPress posts with Post ID, Title (raw), Status, URL, Publication date (GMT) and Modified (GMT), and keep the published ones.

  2. Inspect the posts Google isn’t showing.

    Run Search Console URL Inspection on every published post with no impressions in the 90 days, up to 100 URLs per read. Keep Index verdict, Index coverage state, Indexing allowed, Page fetch state, Last crawl time, Google canonical URL and Declared canonical URL. URL Inspection shows Google’s indexed version, not a live test, and Google allows 2,000 inspections per property per day. Match all three sources on the normalized URL: lowercase the host, drop query strings and fragments, and compare with and without the trailing slash. List any post that one source doesn’t have, because a post the crawler never reached is evidence too.

  3. Put each post in one bucket, then fix it.

    Check causes in order, because an earlier one hides the later ones. Not indexed or technical comes from URL Inspection and the audit: a noindex, a canonical pointing elsewhere or Google choosing another URL is technical; crawled or discovered and not indexed is not indexed. Then broken internal links. Then thin (under 600 words) or out of date (not edited in 12 months). Then whether the post gets any impressions for the query it was written for, and if it does, whether that query sits past position 40. The assistant proposes the fix for each post, you approve it, and Datapipe makes it in WordPress and records it in the change history.

See the complete example report
EXAMPLE REPORT

Why is my website not showing up on Google?

Search Console Aug 21–Nov 18, 2026 · Audit Nov 16 · Inspected Nov 18

Why is my website not showing up on Google?
CausePostsWhat fixes it
Not indexed8Content and links
Technical problem4WordPress and SEO plugin
Past position 404Links, not rewrites
WHAT TO LOOK ATOf 48 published posts, 22 aren’t found on Google for the search they were written for. 8 aren’t indexed at all, 4 have a technical problem, 3 are thin or out of date, 3 show up for a different search, and 4 are indexed and matched but sit past position 40, where a rewrite won’t help. The other 26 are indexed and show up in the top 40 for their search.

Put each post in one bucket, then fix it.

URL Inspection shows 3 posts as Crawled - currently not indexed: the overtime calculator guide has 380 words, the restaurant tips post 450, and the shift swap policy template repeats the shift swap rules post closely enough that PageOptimized flags it as duplicate content. Three more are Discovered - currently not indexed: Google knows them but hasn’t crawled them, and each sits 5 or 6 clicks from the home page. Two are unknown to Google. The clopening post was published on Nov 14, so that is only time. The four-day work week post is in no sitemap and nothing links to it, so PageOptimized never crawled it either. The payroll export guide has a noindex tag, and Indexing allowed shows BLOCKED_BY_META_TAG, while PageOptimized counts 5 internal links pointing to it. The team availability form declares the availability template as its canonical, so Google indexes that instead. For the meal and rest break laws post, Google chose the meal break laws post as canonical, because both have the same title and this one has no H1. The labor cost percentage post is indexed with 2,900 impressions at position 11.4, but 3 of its internal links return 404. The minimum wage post was last edited on Jan 6, 2025 and its title still says 2025; it has 4,100 impressions at position 18.6, and searches for 2026 increases already reach it at position 24.9. The predictive scheduling post was last edited in March 2025. The split shift post has 410 words and sits at position 26.3 for split shift. The shift planning checklist post gets 3,300 impressions, all for shift templates, because its title is about shipping shift templates. The work schedule post is titled Scheduling made simple and never appears for how to make a work schedule. The on-call template post is titled as a product announcement and appears only for on-call rotation searches. Employee scheduling software sits at position 58.3, shift scheduling app at 47.9, staff rota software at 63.1 and the workforce management guide at 44.6. Each is indexed, edited since July 2026, over 2,200 words and free of audit problems, and its main impressions come from exactly the query it targets. These are competitive product searches, and the pages that rank have far more sites linking to them.

Try the example with sample CSVs

Fictional rows matching the example above. Attach these files to your assistant for a sample analysis.

Data method, reporting checks & sources

Add your PageOptimized project, your Search Console property and your WordPress site to one Datapipe project. From PageOptimized, read Site audits to find the latest completed audit, then Audit crawled pages (Page URL, HTTP status code, Canonical URL, Word count, Internal links, Indexable, In sitemap, Crawl depth) and Audit issues (Page URL, Issue type, Severity) for that audit. From Search Console, read clicks, impressions and position by page, then by page and query, for the last 90 days; Google reports those dates in Pacific time and leaves out rare queries. From WordPress, read WordPress posts with Post ID, Title (raw), Status, URL, Publication date (GMT) and Modified (GMT), and keep the published ones. Run Search Console URL Inspection on every published post with no impressions in the 90 days, up to 100 URLs per read. Keep Index verdict, Index coverage state, Indexing allowed, Page fetch state, Last crawl time, Google canonical URL and Declared canonical URL. URL Inspection shows Google’s indexed version, not a live test, and Google allows 2,000 inspections per property per day. Match all three sources on the normalized URL: lowercase the host, drop query strings and fragments, and compare with and without the trailing slash. List any post that one source doesn’t have, because a post the crawler never reached is evidence too. Check causes in order, because an earlier one hides the later ones. Not indexed or technical comes from URL Inspection and the audit: a noindex, a canonical pointing elsewhere or Google choosing another URL is technical; crawled or discovered and not indexed is not indexed. Then broken internal links. Then thin (under 600 words) or out of date (not edited in 12 months). Then whether the post gets any impressions for the query it was written for, and if it does, whether that query sits past position 40. The assistant proposes the fix for each post, you approve it, and Datapipe makes it in WordPress and records it in the change history.

The three sources are matched on the normalized URL, and posts missing from the audit or from Search Console are listed, not dropped. URL Inspection is Google’s indexed version, not a live test; it is run only on posts with no impressions, within the 100-URL read and Google’s daily inspection limit. Each post gets exactly one bucket, checked in order, so a noindexed post is never sent for a rewrite. A missing Search Console query row means Google left it out or showed nothing, not that nobody searches for it; average position is weighted by impressions and isn’t a fixed rank.

  • The three sources are matched on the normalized URL, and posts missing from the audit or from Search Console are listed, not dropped.
  • URL Inspection is Google’s indexed version, not a live test; it is run only on posts with no impressions, within the 100-URL read and Google’s daily inspection limit.
  • Each post gets exactly one bucket, checked in order, so a noindexed post is never sent for a rewrite.
  • A missing Search Console query row means Google left it out or showed nothing, not that nobody searches for it; average position is weighted by impressions and isn’t a fixed rank.
  • Access to the intended PageOptimized account or property.
  • Access to the intended Search Console account or property.
  • Access to the intended WordPress account or property.
  • The three sources are matched on the normalized URL, and posts missing from the audit or from Search Console are listed, not dropped.

For blended reports, align dates, normalized URLs, and reporting grain. Query-level search rows must not duplicate page-level sessions.

A FEW USEFUL ANSWERS

Before you start.

Why is my website not showing up on Google at all?

If even your brand name finds nothing, check the whole site first: a noindex on every page, robots.txt blocking Google, or a site so new that Google hasn’t found it. Search Console’s Pages report and URL Inspection on your home page answer that in minutes. This use case is for the more common case: the site is on Google, but particular pages aren’t.

What does Crawled - currently not indexed mean?

Google fetched the page and decided not to add it to the index for now. It is usually a judgement about the page: thin, very close to another page on your site, or not linked from anywhere important. Requesting indexing again without changing the page rarely helps; make the page clearly useful and distinct first.

What does Discovered - currently not indexed mean?

Google knows the URL exists but hasn’t crawled it yet. On a small site that usually means the page is hard to reach: few internal links and many clicks from the home page. Links from posts that already rank are the fastest fix.

Why do I need PageOptimized if Search Console has URL Inspection?

URL Inspection says what Google did with a page. The audit says what is on the page and around it: word count, canonical, internal links, crawl depth and whether it is in the sitemap. One explains the other. A post the crawler never reached at all is a strong sign nothing links to it.

Can the assistant request indexing in Google for me?

No. Google offers request indexing in the Search Console interface, not through the Search Console API that Datapipe uses. The assistant can resubmit your sitemap in Search Console and, if you add Bing Webmaster Tools, submit changed URLs to Bing.

Will rewriting a post fix a ranking past position 40?

Usually not when the post is indexed, current, matched to the query and free of audit problems. For competitive searches, the pages above it tend to have more and better sites linking to them. That is why those posts get internal links and an outreach work item instead of a rewrite.

YOUR NEXT STEP

Try it with your own data.

Start free with up to 3 data sources. No credit card.

Start free →