Welcome to the Q&A Forum

Thanks I'll check it right away.

As I claimed, it's a discussion not yes or no answer. Here are my two cents - I usually use the self-referral canonical to avoid and more duplicates, just like any other pages. I'll give you a quick example: Lets say you have this page: example.com/shoes?p=1 In case I use the other filters onsite (very common to eCommerce sites) it might look like this: example.com/shoes?p=1&type=nike&color=red To avoid this I use the self-referral canonical anyway.

If image search is important to you, I would suggest creating 301 redirects for all image URLs. Unfortunately, there's not an easier answer than that, especially on a self-hosted platform. If you aren't able to do that then you'll need to get by with simply uploading a new image sitemap to Google webmaster tools, and start fixing the 404 errors manually when they show up in GWT. Assuming your pages are 301ing to the new URL, then Google should find the new images pretty quickly, but might take awhile to gain rankings back.

Hi David, sorry i only check the forums on weekdays. I don't use wordpress on a regular basis so my knowledge to hand isn't the best. But everything you need to do to set up yaost or most other SEO plugins have really good tutorial videos on youtube. https://www.youtube.com/results?search_query=seo+yoast+tutorial+2015 The top few hold  your hand through the basic installations and set-ups and should take you 90% of the way. Sorry its not a direct solution.

Thanks for getting back to me Patrick, what we are really looking for is a good platform that allows us to optimize for SEO (keywords, metadata etc etc). Desk doesn't allow much tweeting in that department, and MadCap Flare is a great information management tool, again outputs in iFrames so is not ideal for allowing Google to crawl the site. I guess what we are after is a great information management tool/website that allows both ease of information management along with the ability to optimise for SEO (I could be asking for too much!) Cheers Matt

The things you make me Google ... I agree - and I checked just to be sure but yes, you should be safe. (On the other hand, ExpertsExchange.com changed their domain name after it was mocked about a billion times. They now have the hyphenated version.)

Thanks all for Inputs I searched Google and found this note from Google which may happen post server migration https://support.google.com/webmasters/answer/6033412?hl=en&ref_topic=6033383 A note about Googlebot’s crawl rate It’s normal to see a temporary drop in Googlebot’s crawl rate immediately after the launch, followed by a steady increase over the next few weeks, potentially to rates that may be higher than from before the move. This fluctuation occurs because we determine crawl rate for a site based on many signals, and these signals change when your hosting changes. As long as Googlebot does not encounter any serious problems or slowdowns when accessing your new serving infrastructure, it will try to crawl your site as fast as necessary and possible. Add on Thompson Paul - Appreciate - yes its a good suggestion, will see to include sitemap

Folding or merging websites should be done when possible. The fact you are on this blog querying same shows that you are properly considering the implications of the fold. Take your time to do it right. Consider all options. A poorly executed fold can have sustained detrimental impact - seen it a few times when Bosses pull the trigger and demand speed & nothing else, no room for thought allowed. I would recommend drawing a site map of both sites and then considering the impact of the re-directs for each page - mapping/planning it out. I know this is about technical and the boys have that covered but also think about brand, mail outs, informing your data base. However you connect with the customers make sure you have that covered. The customer comes first. Finally on examples - we have done several mainly eCommerce sites where the blog has been a separate URL not even a sub-domain. None have gone backwards and a couple of them popped immediately after the fold. Ultimately great outcomes for all.  So I have confidence. Just make sure you are doing what you are doing now considering the unique aspects of your website and how you will capture those aspects in the fold. Good luck.

It's not a secret that Google can use Chrome anyway that it wants for data collecting. Just read the TOS.

Hi there If you have a search console profile for that .net URL, you could use the Change of Address tool to let crawlers know the site has moved. I would also check this migration guide to see if there are any loose ends that may still be indexing those pages. Sometimes you can have internal links or sitemap issues that may still contain old URLs. Lastly, there is the remove outdated content from Google tool, but I would make sure that your new URL / domain are appearing for all searches that you need it to be, and that the .net address isn't. Hope this helps! Good luck!

Hi Luke, Just make sure that your robots.txt file located at https://www.example.com/robots.txt doesn't block search engine spiders. Of course there may be some folders or filetypes you want to block but it certainly shouldn't look like below which would block everything: User-agent: * Disallow: / Hope that helps

Google talks about this as part of Dynamic Serving of content. Here is their article, which also includes tips on how to distinguish user agents (including how to signal this to Google): https://developers.google.com/webmasters/mobile-sites/mobile-seo/configurations/dynamic-serving This is an okay practice and I'd not had any Google penalties when I've utilized it. The big concern with doing this type of dynamic content shift for different devices is to avoid cloaking, which Google mentions in that article as well (be sure to click on the link in that Dynamic Serving article for more about cloaking). So long as you avoid cloaking, you should be in okay territory. My advice is to test out your user agent matches thoroughly - I'd even go so far as to try this on one or two pages with some simple changes for each user agent and then make sure Google indexes those pages correctly before rolling this out to your entire site. Hope that helps.

As Joost said, you should not block access to files with help in the reading / rendering of the page. Looking at your Robots file, I would look at the following two exclusions. Do they block anything else that runs on a live page that Google should be seeing? Disallow: /includes/ Disallow: /scripts/ -Andy

Hi, To add to all the good advice given so far, you can also utilise URL Parameters in WMT Search Console to specify that a cert URL pattern is canonical content. Kind Regards Jimmy

Indeed.com uses the double hyphen in their URL scheme and it certainly doesn't seem to hurt them.  I Imagine this is due to being able to reconstitute this back from URL rewriting so they know the difference between a dash in the URL that replaces a "space" vs a -- which would reconstitute back to a dash. Example:q-Tennis-Channel-jobs.html Maps back to the company Tennis Channel Example: /cmp/Sag--aftra Maps back to the company Sag-Aftra

You could display all of it and make some clever use of jump links. Just sayin...

Yes, it is as simple as www.rootdomain.com/blog - here is an example of a fashion retailer site doing it right for you to review http://www.cottonongroup.com.au/news/featured-news Yes, rootdomain/article - The content transfer depends on how content is hosted, structured etc. but it is straight manual labour moving the content across. Hope that assists. The positive is once you can dedicate all resources to building the domain authority in one domain - you usually get greater reward for effort.

Everyone is correct the Title Tag is more important than the description.   You should also consider you H1 in context of your title tag as that is also important. On the description that has no or nominal SEO impact. So as  Patrick states this is where you take the opportunity to focus on CTR or a CTA. Your sample tag - does not include the brand name, so google will likely draw that in. So Patrick's suggestions should be considered Page | Category | Brand I would think that you are shooting yourself in the foot including monthly figures and square foot in the title unless that is a key way people search for the space in the US - i would think  Greenwich Village | Office Space Rental | Brand.  That is what I would recommend.  Cover suburb, geo-specific and key words office space and then brand... I am not sure I would even list size etc in the description, but leave with you.

Hi there If you configured this properly, I wouldn't worry about this at all. Check your internal links and sitemap to make sure that your URLs listed as a reflection of this www. version. Beyond that, you're all good, no need to block non www. Hope this helps! Good luck!

If you have a very small blog, with a limited number of posts on a narrow topic range, this perhaps doesn't apply. If you are bigger than that and cover a range of topics, a multilevel structure keeps things organized, for you, your readers, and for search engines. You can also take advantage of internal linking, organizing sub-topics under topics both so that readers can find related articles that might interest them and so that search engines can see how your posts are related, and what concepts are relevant. [A post titled "Shingles" would mean one thing under health-news, and another under building-materials.]