Welcome to the Q&A Forum
Browse the forum for helpful insights and fresh discussions about all things SEO.
Hi,
Have you tried qualifying clicks through meta description and title tag copy? I've had pretty good success using this tactic for local businesses to deter clicks outside of their service area - because a similar problems exists where you can't add negative geographies for where organic results will show.
Hi,
Google Analytics is pretty good about assigning proper attribution to channels. If you had been sending out emails prior to tagging the links, that traffic was falling under either Direct or (Other).
PPC is the only medium that would cannibalize organic since you can have impressions in both spaces at the same time. The drop in organic traffic could just be the ebb and flow of your business. Since most businesses have seasonality, year over year comparison is often a better yard stick for performance.
Is there a particular search engine that you can attribute the traffic loss to? Or perhaps a piece of content received more entrances last week simply due to the timeliness of that content?
If you're able to predict your links that easily, they're probably not very good links and therefore won't contribute much to the DA of your site.
Since your blog is on a subdomain, yes, you will need to set up a separate WMT profile for it. The blog will also need its own robots.txt and XML sitemap files, since technically speaking, subdomains are regarded as a different site.
Hi Joe,
Specifically addressing your first question, 301 redirects that take URLs to HTTPS won't cause any loss in link juice as they would with a typical 301 redirect. This information came out of a Q&A with Mueller, which you can read more of here.
For your second question, that largely depends on your server, but you should be able to do this with a single rule, as opposed to redirects on a one-to-one basis.
HI,
You might want to try adding the NOODP tag across all pages on your site.
This tag will allow you to 'opt-out' of Google filling in this data for you. The ODP in that stands for Open Directory Project, aka Dmoz, which is where Google grabs this information from if it feels your titles and descriptions aren't the best.
I think the solution you're looking for is pagination markup. Use the rel=prev and rel=next tag to point search engines towards the proper paginated URLs. This effectively eliminates duplicate content issues where http://3mil.co.uk/insights-web-design-blog/page/3/ is flagged as a duplicate of http://3mil.co.uk/insights-web-design-blog/page/2/.
You can read more on this topic in this article on the Search Console help site.
I'd recommend keeping it on the site. This type of content has a good chance at garnering some quality links, so you don't want to dilute their value by redirecting.
Since your content is very time-relevant, it would be very beneficial to your users to include this information. It could also help with organic long-tail queries, in the case where someone searchers 'fashion trends for summer 2016'. You're currently not providing the date information, so your chances of appearing for that query are much lower than if you had date-published info directly on the page.
Those blogs posts are going to be your long-tail keywords, so the more specific you get with the keywords that you target, the better. Put yourself in the mindset of someone who would benefit from that content, then try to think about what you would search for to get to that content. For example, for your post "Steps to follow in buying a CRM", some qualified queries might be "things to consider when choosing a CRM", "how to choose a CRM", "what do I need to know before buying a CRM".
Hi Luke,
I've had many clients in the same situation. The approach I typically take is to split up the street address between a Suite A and Suite B (or some similar variation of that). Google is still able to pinpoint the geographic location of the business, but also recognizes that they're not identical.
Hi,
Your statement "I know that targeting more than one keyword per page in a website leads to keyword cannibalization" is close, but not quite true. Keyword cannibalization happen you talk about the same topic or keyword set across multiple pages, search engines aren't sure which to rank higher, so they usually opt for none of them.
Content should be centered around topics these days, not keywords. Based on the sample blog topics you shared, it seems like you're doing that quite well. You're still talking about CRMs but in different ways, so I think your strategy is good.
You're in the driver's seat here. _You _have the content _they _want. If you lay down your requirements and they don't want to play, then don't give them permission to use your content. It's really that simple. You're gaining nothing here with their rules, and they gain a lot. You should both be winning in this situation.
Adding nofollow to links that point to dictionary pages will prevent search engines from getting there, but since the pages are in the index (and you don't want to change that) you're still facing the duplicate content issue.
I know it's a huge project to take on to add content to these pages, but it seems as though it's your only option. Perhaps you could split the project up between a few people and each update one page per day. That way it doesn't turn into a major time-suck.
No problem! I meant to mention this in my first comment, but I also noticed that there's no robots.txt file in place. That's obviously not going to help your indexation problem too much, but nonetheless something you should know about.
You can do that, but you should check Google Analytics to see how many organic entrances you get to these dictionary pages first. If a lot of people enter your site that way, rel=canonical is going to hurt your traffic numbers significantly. For example, when you add a canonical tag to this page (http://anglu24.lt/zodynas/a-suitcase-lagaminas) that points elsewhere, the suitcase page is going to get dropped from the index.
The ideal situation would be to create more unique content on these pages. You're getting duplicate errors because more than 90% of the source code on the dictionary pages is a match. When you consider the header and footer, and the other code for the template, it's the same everywhere. The dictionary pages are very thin on content, so it's not enough to differentiate. If you can, build out the content more.
Here's a few ways you might add more content to each dictionary page:
Looks to me like Google can't properly access your XML sitemap. I tried to put it into 2 different validator tools and URI Valet and none of those tools were able to access it. It could be something with HTTPS. Did you recently switch the site over to secure?