Post navigation

I just checked my Google Search Console and under Crawl, Fetch as Google I see my site status is showing as redirected, with a yellow sign beside it!

What does that mean and how can I fix it, please?

Regards
Zara

————————————–

Hi Zara

First up, don’t panic. The *Fetch as Google* tool simply tries to imitate what Googlebot sees when it crawls your site code. It doesn’t mean that Google can’t index your site. If you are still seeing data in the Search Console relating to your site status, all is well. If there were major indexing issues, you would see errors in the Crawl Errors and Site Appearance categories.

As for WHY you are seeing a redirect status, without knowing your site URL, I can only guess. But I’m confident it will be one of these reasons:

1) Domain canonicalization: Does your site load using both http:// and http://www. or does one version redirect to the other? Have you set a preferred domain in Google Search Console? To do this you need to set up views for both versions in Google Search Console and then set your preference. After you’ve done that, depending on which domain version you open within the Console, the *Fetch as Google* tool will show a different status.

1) Fetch as Google results for http://www.searchenginecollege.com

2) Fetch as Google results for http://searchenginecollege.com

For example, to avoid duplicate content issues in Google, I have set a) http://www.searchenginecollege.com as my preferred domain in my Search Console, but I also have a Console view for b) http://searchenginecollege.com. On the server side, I have set the non www version to redirect to the www version. This is known by several names, including URL redirecting, domain masking, piggy-backing and parking. If I fetch a) as Google, I see the status as shown in the first image. If I fetch b) as Google, I see the yellow *redirected* status as shown in the second image.

2) 301 or 302 redirects: Have you recently switched domains? Although Googlebot follows redirects, the *Fetch as Google* tool does not. So if your site was originally set up in the Google Search Console as one domain e.g. http://www.siteA.com but has now moved to http://www.siteB.com and you set up a 301 or 302 redirect server side, then if you are looking at the original site view in the Console, it will show up as redirected in the crawl tool. You can inspect the HTTP response on the fetch details page to see the redirect details. Learn how to do this.

3) Moving to SSL: If you have recently updated your site from http:// to https:// and you’re seeing *redirected* in the crawl status, you may have the same domain canonicalization issue as 1). So you need to set up a view for the https:// version of your site in Google Search Console. More info on SSL issues here and here.

It’s Tim here. I’m the developer for a website – [URL removed for privacy reasons] – and as of Thursday or Friday last week, Google has crawled my whole site. It shouldn’t have been able to do this, but it has.

Part of the site is written in PHP and Google has cached all the pages, several of which contain information that shouldn’t really be in the public domain.

I’ve submitted the FQDN to Google asking them to remove the URL which will hopefully prevent any results being shown in a Google search. The request is currently in a ‘pending’ state and I’m wondering how long this would actually take to be purged.

Thanks,

Tim

————————————–

Hi Tim

I’ve not personally lodged a take down request with Google, so I’m afraid I’m not speaking from experience, however I’ve had colleagues tell me this can take up to 3 months if a site has already been crawled.

Your email doesn’t make it clear what happened, but it may also depend on how sensitive the content is and why it was indexed in the first place.

A couple of things you can do while you’re waiting:

1) If Google managed to crawl your whole site, you might have conflicting instructions in your robots.txt file, your robots meta tags on those pages or you might be including content you don’t want public in your sitemap.xml file that Google is indexing. Check all those areas so the problem doesn’t re-occur.

2) Ask Google to remove content through the Webmaster Search Console. This is often faster than the formal take down request you submitted via email. It requires you to verify ownership / admin of the site via the Search Console first.

Keep in mind that even after you’ve blocked the pages from being indexed, they can take a while to fall off the Google search results, depending on the number of data-centers that have cached them and where they are serving results from.

I’ve read that Google ignores them, but I’ve seen commas as well as full stops (periods) used in title tags as a way to separate keywords for Google and not just visually.

For example:

< title > Acme Company. SEO service in New York, SEO audit New York.< /title >

Here we have two different and distinct keyword phrases: “SEO service in New York” and “SEO audit New York”. It is clear enough.

If Google ignores full stops and commas, there are many more keywords: “SEO service”, “New York”, “SEO in New York”, “SEO New York”, “audit in New York”, “SEO” and so on…

I know that the best practice is to optimize each page for 1 or 2 keywords, certainly not more than 3 keywords. So what is your opinion on the use of commas and full stops to separate keywords in the title tag?

Thank you in advance!

Max

————————————–

Hi Max

First up, the impact on search results of using punctuation in title tags is minimal. Google usually ignores commas and separation symbols. You should use punctuation primarily to write grammatically correct titles that make sense to humans.

Commas (,) should be used as commas, not separators. Full stops should be used to end a logical sentence. However, pipes (|) and hyphens (-) can be used as separators. Colons (:) aren’t ignored and imply to search engines that what follows is a subtitle or explanation / elaboration. Hyphens can also sometimes be interpreted as colons. As a separator, the pipe is usually preferable to use because of its small pixel width.

Having said all that, the best option is to use as little keyword real estate as possible in your title tag, so that means combining your keywords into phrases that cover several individual keywords / phrases and not repeating keywords unnecessarily.

So, for example, if you are targeting the 2 phrases: “SEO service in New York” and “SEO audit New York”, then I would create the title tag as follows:

1) < title > SEO services and audits in New York City | Acme Company < /title >

instead of the longer:

2) < title > Acme Company: SEO service in New York and SEO audit New York < /title >

Notice that my version takes up less space, but now has no keyword repetition and includes the plurals *services* and *audits* as well as the longer *New York City* instead of the shortened version. This means that my title tag is optimized for a wider range of search terms, even though it is shorter in character length. It also includes the company name at the end of the tag, separated by a pipe.

In fact, a better version might be:

< title > Search engine optimization services and SEO audits in New York City | Acme Company < /title >

Although longer, this still falls within the accepted character count for the title and would be a relevant match for search queries by persons using the long form *search engine optimization* as well as the shortened version *SEO*.

If you’re a regular reader of this blog, you’ll know that I’m a big fan of time-saving tools and short cuts that can make life easier for digital marketers.

On a recent trip down the rabbit hole of online marketing blogs, I came across the a tidy collection of SEO resources collated by Amar Hussain of website broking company FE International.

Pitched as the ultimate toolkit for digital marketers, the collection is unique in that all of the resources are free. This is great news for marketers on a budget and ideal for my SEO students, many of whom are still in college or on low incomes.

Each of the resources are categorized along the following themes:

A/B Testing

Analytics

Competitor Analysis

Content

Diagnostic

Email

Infographics

Keyword Research

Link Research / Link Building

Local SEO

Resources

SERP Tracking

Speed

Technical

Toolbars / Extensions

WordPress Plugins

While there are many tools in the list that I know well, I was pleasantly surprised to see a large number that I haven’t seen before and can add to my own toolkit. Of these, Optimizely, WordSmith and Five Second Test were the most exciting finds.

I awoke on Day 13 with a renewed sense of purpose and a determination to impress my first Elance client. After logging in to the Elance system, I switched on Tracker with Work View and got started on setting up Analytics benchmark metrics and KPIs.

Around midday I received a phone call from another client and spent about 30 minutes surreptitiously checking my Facebook while trying to decipher what she was actually calling about. I still don’t know. Unfortunately, I had left Work View on while she called and now there were several screen-shots of my Facebook page displayed in my Elance project. Fumbletruck.

Thankfully, I learned there was a way to remove screen-shots from Work View, but you have to sacrifice any time tracked during the same session as the screen-shot was taken. Ouch. I ended up losing about 20 minutes authentic work time, but learned my lesson (or so I thought).

Meanwhile, my potential Hawaiian client had gone suspiciously quiet. Given his enthusiasm, I had spent nearly 4 hours auditing his AdWords account and preparing a detailed proposal to address all the issues. But I hadn’t heard anything for a few days. So I sent him a Skype message to see what was going on. In return I got: “Will keep you in the loop..next few days..super busy. We do need help, just working on the puzzle to add you in! Much Mahalo”. Hmmmm. Maybe I should stop mentally packing my bikinis for Honolulu. But I figured I could live with a few days delay.

So back to Elance I went, logging in to find I’d been invited to pitch for a job working with Gelato. Or maybe it was Velato. (Why oh why couldn’t it have been Gelato?). Anyway, it was some programming language that I have absolutely no skills in whatsoever. Why the client deemed me a suitable match for the job, I’ve got no idea. Maybe he thought it was Gelato too (my ice-cream eating abilities having obviously been syndicated via Instagram). Whatever. But I’ll never know as I turned it down.

But now I had serious sugar cravings and went on a search quest to find the perfect gluten-free caramel slice recipe. I found it at the exact same moment that a little Work View window popped up to take a screen capture. Funglebum. I had two choices: 1) do nothing and hope my Elance client really likes caramel slice or 2) remove yet more screen-shots from Work View. Le sigh. Yeah, you can guess the option I went for. I’ll say this for Work View – it keeps you accountable. And hungry. So very, very hungry.

Day 13 ended with me working to midnight for my client, not making caramel slice and conducting SEO keyword research about tampons and maxi-pads. I’m truly living the dream.