Google not indexing pages

[QuickRon]

We launched our Miva site over 8 months ago. At that time, we set up Google Search Console as well as our sitemap in Miva. And we set up the task to run the sitemap every week. At this point, Google has indexed only 1/3 of our pages.

There are over 2,300 pages that are listed as "Discovered - currently not indexed" in GSC.

I know that it can take time for Google to index a larger site ... but it seems like it's taking an excessively long amount of time for our site.

Any ideas or suggestions on how we can get all our pages indexed sooner?

Thank you,
Ron

[lesliekirk]

I'm going to tag along for the ride. I have a couple of sites that have the same issue.

[sartaingerous]

Hi Ron and Leslie! Please create a ticket for the sites with Miva TAC in my.miva.com and we will take a look.
-The Miva Team

[QuickRon]

Hi sartaingerous.
I did open a support ticket with Miva many months ago, when I first noticed pages were not being indexed, and they said it was a Google issue and not related to Miva ... and basically sent me to Google. And that was a dead end. I've never had an issue before with a site not getting fully indexed.

I'll open a new ticket and reference this post.

lesliekirk thank you for letting us know you're having similar issues

[Nick]

I was able to work with QuickRon and found that a number of URLs were labeled as "Discovered - currently not indexed". The majority of the URLs were product pages.

When adding the product URLs to Google Rich Text Test, https://search.google.com/test/rich-results, there were errors returning in the results.

Rich text errors on your webpage may not directly prevent it from being indexed by Google, but they can negatively impact your website's search engine ranking and user experience, which could indirectly affect its visibility on Google's search results.

The error was regarding the value in the itemprop="itemCondition" having a value of "new" instead of "NewCondition". This issue has been reported as a bug in the Shadows framework and will be updated in the next Shadows release. The itemprop="itemCondition" is found in the PROD display template.

Since the store was using an outdated version of Shadows it also included a JavaScript resource called "product-json-ld" which needed to be updated as well (note the current version of Shadows does not include the JavaScript resource).

[lesliekirk]

FYI - I did a spot check on the store I alluded to. The pages are just sitting in Google purgatory don't have rich text errors and are available for indexing.

[Nick]

FYI - I did a spot check on the store I alluded to. The pages are just sitting in Google purgatory don't have rich text errors and are available for indexing.

Can you confirm that all the pages are included in the sitemap.

[lesliekirk]

Can you confirm that all the pages are included in the sitemap.

Yes, they are.