2

In Search Console > HTML improvements > Duplicate meta descriptions I have errors of pages that I have a redirection in the .htaccess. I mean the Search Console see as duplicate the old page that does not exists anymore and the new page that substitutes it.

As I said, I redirected the old page to the new one in the .htaccess. I have the .htaccess in the root of the site. I have checked that the redirection works well. I have checked that there is no link in my site that points to the old page. Is there anything else I should do?

I improved the title of the page, the URL and, at the same time, made the redirection in January 2017. Now is May 30, 2017. I know that the Search Console needs time but, isn't that too much?

  • What type of redirect? 302 temporary or 301 permanent? That sometimes matters for Google. – Stephen Ostermiller May 30 '17 at 17:03
  • @DocRoot. You are right, sorry. I updated – Nrc May 31 '17 at 7:01
  • @Stephen I made a 301 in the .htacess – Nrc May 31 '17 at 7:01
1

I have checked that the redirection works well. I have checked that there is no link in my site that points to the old page. Is there anything else I should do?

Yes. Check again. If you have an advanced setup like myself, you can use a command line tool like curl to check a webpage and see if it returns correct data. A page with malformed headers and/or data can confuse google.

Visit this site: https://redbot.org/

Then enter a URL that is supposed to redirect to another URL. When you hit submit, you'll see the headers that are returned.

If you see the following lines:

HTTP/1.1 301 Moved Permanently
Location: http://example.com/new

and the Location line is somewhere in the headers and "http://example.com/new" is replaced with the actual URL of your page, then you're on the right track.

Now put in the new URL and hit submit and you should see the following line at the top of the headers:

HTTP/1.1 200 OK

The only variances in the HTTP/1.1 protocol allowed is that the OK after 200 can be changed to something different, and same goes with "Moved permanently".

HTTP/2.0 might produce different results but the idea is the same. One page returns headers that instruct a browser to redirect automatically, and another page returns headers that instruct a browser that there is content on the page to display to the guest.

Just for sanity purposes, I'd recommend using apache's built-in redirection pages since the title tag of that page is different from what you would use for your pages.

  • I tried that and I think everything is ok. I do not understand your last paragraph what are the "apache built-in redirection pages" ? – Nrc May 31 '17 at 13:50
  • by that, I mean the pages that are served internally from the apache server (instead of custom created error pages) when there's a problem loading a page. – Mike May 31 '17 at 14:41
  • Do you mean that is not a good idea to have a custom made 404 error page? – Nrc May 31 '17 at 16:40
0

Normally it doesn't take that long to see changes.. but sometimes it can be very slow.

  1. Try to fetch and render (Google Search Console) the original page url to see if Google can see the redirect you have created and/or if other helpful messages appear.
  2. Then choose to index the page.

That will usually do the trick.

  • I have clicked to the pages in the search console and the redirect works well. I do not understand your second point, what do you mean index the page in this case? Should I do anything or you just mean that I should let Google do their job? – Nrc Jun 1 '17 at 14:52
  • After you manually fetch and render (1) (either as Desktop or Mobile) you get the option to "Submit to index". Then a window appears where you can choose if you wish to Crawl only this URL, or if you also would like to crawl its direct links. Pick the first one. Then wait for the result. – Kristian Svensson Jun 1 '17 at 20:37

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.