Hi Chuck,

I would also look into categorizing your URL parameters in this case: https://support.google.com/webmasters/answer/6080550?hl=en as this is inovlving both sorting and categorizing the data on the page it's a good solution to tell Google more about the intent that you have on this page.

Martijn.

What Jordan says, getting the Schema wrong is just unfortunate but it shouldn't hurt you.

Hi,

I would mostly look into the site itself, from what you've mentioned here I don't think that the problem is in your sitemap but more on the side or React. Are you using server side or client side rendering for the pages in React? That usually can have a big impact on how Google is able to see the different pages and pick up on content (including meta tags).

Martijn.

Hi Roman,

Ok great, you're at least also of the opinion that bigger sites will need an actual implementation. I want to make sure to at least mention these articles too, to not give people the idea that they should all go ahead to implement it through GTM, as it's still not a recommended way to go:

• https://www.upbuild.io/blog/dont-use-gtm-for-structured-data/
• http://www.thesempost.com/google-dont-rely-google-tag-manager-structured-data/
• https://www.seroundtable.com/google-google-tag-manager-seo-24984.html (see the Tweets mentioned in this article, it's based on John Muellers reply to my Tweet about all the down sides of implementing GTM for structured data).

Google Tag Manager? Which is not recommended by Google at all for structured data implementations?

Look into itemList in combination with Product Schema.org, what you could do here is make sure that the template in WordPress has this embedded in the code. So, in that case, you'll make sure that the content is marked up in the right way and you don't have to worry about it when you have content that is being deleted/updated/removed.

To answer your question: "Does anyone know if search console errors showing as follows are damaging to SERPS." - No, this would almost be impossible. The errors that you're mentioning are just two core pages of WordPress that cause some errors where the 400 error is actually supposed to happen as it's not a URL that is just accessible like this. It's a file that is being used to make AJAX requests.

The fact that this potentially coincides with a uplift/drop in rankings is probably caused by something else.

Sometimes the cached pages aren't the actual representation of the page that you're looking for as some of the assets can't be loaded. What I do is go into Google Search Console and try to Fetch as Google for the same page you just tried to look up as the cached version. Then check what the response is and if that matches, often it's not the case and the page will fetch just as you see it as a user. With some of the more modern techniques it's possible that the page wont' render correctly in a cached version versus the live version.

NO, this is not hurting your ranking score. UTM parameters are being used for tracking purposes but won't have any influence on the pages. If you want to be absolutely sure about this you can do two easy things:

1. Tell the crawler in Google Search Console that these parameters don't influence anything, you can read more about it here.
2. Use canonical tags, which you already seem to have, so you should be good.

It's not additional CSS, it's just a set of different characters (

@Keith, were you able to figure out the solution to this problem?

Keith, it seems that speciality is not a valid property. The documentation doesn't mention it at all, so I would look into using MedicalSpecialty which you can find more information right here: http://health-lifesci.schema.org/medicalSpecialty

Quick question, have you also added the subdomain on your CDN to Google Search Console to see if you can find any additional information on your URLs in there? It sometimes something that people forget to do, a CDN doesn't always open up to a search engine (although it should).

I would for sure experiment with this, I'm working an industry where 'near me' keywords are incredibly popular. We've even created specific landing pages for them so we can target people with a specific question. Usually you won't be able to rank product or category pages just with these keywords on the page. They'll need to be specific to answer the user intent.

In regards to Nicholas, yes they'll understand the location and can use that. But it doesn't mean certain pages are the right ones to rank for that query. The question remains then if just adding it to the title will help enough.

No, I would make sure it's the best use case for you. Sometimes you can store this data in a cookie. But there are still great ways for just SEO that can help you with making sure that it won't hurt. Usually the best way is still having a canonical tag on the page that matches with the page that the content is originally from.

Well it would depend on how you set up the data. In the end you can transfer the data from one page to the other in multiple ways (local data storage, cookies, POST). So in most cases you wouldn't even need a parameter like this so you can keep your URLs as clean as possible.

Hi,

Parameters are definitely not always a bad thing, if you use them for filtering or pagination they have a great use case. Also for tracking purposes which I think is what you're talking about here it would be fine. But you probably want to put some support in place to make sure you don't mess up your SEO. You have a few ways of doing that:

• Define the URL parameters in Google Search Console, read more about it here.
• In some cases if it's just for tracking purposes but would trigger an actual pageview or 200 status code. Then it might be good to implement a canonical URL that would link back to the original page.
• Robots.txt, way more aggressive but if you don't want search engines to look at the pages at all you can exclude the parameters through the robots.txt. I would advise against using this if you don't have great SEO knowledge.

Hope this was useful!