Welcome to the Q&A Forum

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).

Shorten and Redirect (With keeping the URL keyword-focused). If there is an opportunity for those website pages to rank for certain relevant searches, I absolutely think it would be worth it to go back in and spend a few minutes optimizing them as well. You can shorten the URLs, create 301 redirects from the old URL to the new one, and then re-optimize the blog posts as a whole, as well as add some internal links with pages you are wanting to improve rankings on. We have seen good results from doing this on our website and it can be an easy win to bumping up rankings for those pages.

Hey, Try fetch and render from Google Search Console. There you could check if there is an X-Robots-Tag in the response header. For reference: https://developers.google.com/search/reference/robots_meta_tag

That's awesome! Glad to know there's a bulk tool out there!

Check Google console whether any error is there. Re-submit your web pages manually in Google search console.

Hi István Sorry for the late reply and thank you for answering the enquiry. I have DM you via Skype by the way.  Actually, last week we have sent a reconsideration after removing all schema, which makes sense when you think about it, but it got rejected after two days. We actually wanted for the schema to show zero after removing the schema before sending the reconsideration. They were using both Microdata and Json+LD on the same and as you can see below it was commented out. Before removing all schemas, their schema codes have been commented out and I do agree there was hidden code, but it was removed. This is the Schema on the homepage: Example for product page Thank you!

You will also have to get those URLs out of the index once you fix the rel next/prev issue. In order to do that effectively, they should return a 404 or 410 status code in the HTTP header so Google knows that they no longer exist (even though they never really did in the first place). Otherwise, it's what is known as a "soft 404" in which the page doesn't really exist, but returns a 200 (OK) status code, which is confusing to Google if you don't want them indexed.

From a product perspective, we tend to need to set guidelines that can be quantified, but I'm afraid the whole truth is never quite that black-and-white. All else being equal, I think keeping your titles to a reasonable length is beneficial. Long titles don't automatically harm you (there's no Capital-P penalty for it), but they tend to create a few problems: (1) Often, long, CMS-generated titles front-load repetitive words (like the site name or category/sub-category), which devalues the unique/important words in Google's eyes and is more likely to make it look like duplicate content. (2) Long titles tend to devalue important words for search visitors as well, which can harm click-through rates. I'm a firm believer that CTR has indirect impact on ranking over time. Even if it had no SEO significance, it's generally bad for engagement and for your site. That said, it depends a lot on what you're dealing with. If a title of a page is, say, a title of a blog post, and it's just a long title, that's probably fine. If you have 5,000 product pages that all start with "Bob's Discount Propane Warehouse | Propane and Propane Accessories | ...", then that's going to be detrimental to your usability and SEO. You mentioned images in your reply to Christy -- could you give a couple of examples of the types of pages and titles you're talking about? In general, image-only pages with no additional content (especially if they have near-duplicate titles) are going to be low-value from a search perspective.

Thank you for your response! I appreciate your input.

Hey Becky–here's a primer on the hreflang tag that I recommend reading: https://moz.com/learn/seo/hreflang-tag Essentially, if you have an international website with localized or translated versions (mexico.website.com, or website.com.mx, or website.com/mexico), you need to use rel="alternate" hreflang="es-mx" (using my Mexico example above) in the head tags of your site's pages.

Hi there, Yes, there are several ways you could do that, but my question is, if it is worth it, or not. If we are talking about a large website, you could have issues with Google's crawl budget. Basically, the crawlers would have to go through an additional 301 to land on your homepage. Google describes their best practices about redirecting 404 pages here: https://support.google.com/webmasters/answer/181708?hl=en If your page is no longer available, and has no clear replacement, it should return a 404 (not found) or 410 (Gone) response code. Either code clearly tells both browsers and search engines that the page doesn’t exist. You can also display a custom 404 page to the user, if appropriate: for example, a page containing a list of your most popular pages, or a link to your homepage. If your page has moved or has a clear replacement, return a 301 (permanent redirect) to redirect the user as appropriate. In my opinion, the decision should be determined by the size of the website. If we are talking about a big website, maybe it would be more beneficial if you follow Google's guidelines, implement a 410 status code. If the website is small, maybe you could redirect the users to the homepage, and hope they are going continue their journey on your website. István

Hi. If it's not showing up, it is probably not defined as a property -- here's a doc that tells you how to add it: https://support.google.com/webmasters/answer/34592?hl=en

Hey, David Butler . . . you are probably the only person who has looked at this issue, so I want to thank you again for your input. I wanted to follow up about this. Since I am using Wordpress for the website, I used Wordpress's rewrite_rule function. After confirming that it was working correctly, I deleted the old sitemaps and created new ones, then  submitted them to Google. Shortly after this, the pages were successfully indexed. So from this experience I get the impression that using URL parameters doesn't necessary work -- I certainly am not going to use them in the future. I am going to mark this issue as resolved.

Thank you so much!!!

Hi there, I'm not 100% sure on this but my guess would be that whatever you're trying to name your channel has already been taken by another channel. I did some digging and it looks like if there is another channel with the same name that has a following YouTube won't let you choose it. Perhaps try searching for the channel name you want and see if it's taken?

Hi there! Thanks for the question. You are correct - at this time the API does not offer a way to call information about Discovered and Lost Links. Link Explorer and the index that supports it, including the API connection, are pretty new and still in beta testing. However, this is a call the team would like to add in the future, so keep an eye out! Please let us know if you have any other questions, or any other features you are interested in seeing added. Thanks!

Hi there! I'm so sorry to hear you're having trouble with MozBar! Sometimes issues like this are caused by extensions in your browser which may be blocking third party cookies- can you double check to make sure that cookies are enabled for moz.com? I have a guide here that may help troubleshoot the issue: https://moz.com/help/guides/research-tools/mozbar#more-help If you're still having trouble, please do send us an email at help@moz.com so we can make sure to get all the info we need to send this on over to our engineering team.

Whenever using SEO tools, use any one tool constantly so that you will not get confused. Each of the seo tools have different algorithms.