Welcome to the Q&A Forum

Nope. No need for images. They just know about the content and link to it. The cached HTML shows they store a copy (or cache) of the HTML though. I could be wrong about the images but that would exponentially increase their storage needs so it seems unlikely.

Hi there What I would do here is review the backlinks that you had pointing to those old pages (you can review this by using tools like Majestic, ahrefs, or Open Site Explorer). Reason being, if some of those links are on sites that get traffic and your link is clicked by a user, they have no where to go - that's a missed opportunity for your business. I would redirect the links with quality backlinks to the most relevant pages on your new site, that way, while not passing along ranking equity at the moment, you still can get quality traffic moving to your site. I'd also reach out to those sites linking to your old URLs and have them update the old link URLs to the new URLs, that way your new pages / site get some link / ranking equity. Does this make sense? Let me know if you have any questions or comments, thanks so much, good luck! Patrick

It is highly unlikely that responsiveness would impact your search rankings at such a high percentage. Unfortunately, without knowing much more about your site it would be hard to look into it. Feel free to PM me more info and Id be happy to take a look.

Hi Johannes, I've understood your question to be about how to treat a site which uses dynamic serving for mobile content. Is this correct? If your site keeps the same URLs for mobile and desktop versions, but serves different content based on user agent, then you will simply need to include a Vary-HTTP header. You can learn more about that here.

Hi, Your 'page 1' URLs should canonicalize to the root level of that page. And your rel=prev tag for page 2 should point to the root, but beyond that, it's standard implementation. Beyond that, the pagination markup for rel=prev/next is pretty simple.

Useful reference links. Many thanks, Mike.

Hi Mike, Ideally, yes, you'd just have the one URL. If you were setting up a site from scratch, I would tell you to avoid having the same content on those two different pages, because we don't want to create any duplication where it isn't strictly necessary. An example of when it is strictly necessary would be something like a ?sort_products parameter which changes the order products are displayed on a page. There's no way to do that without some duplication, so the canonical tag is useful. It's good practice to avoid having more versions of the page than you need because it reduces the number of ways things can go wrong. But as this structure is already in place and seems to be working OK -- only one version of the page is indexed -- I would leave it as it is. Messing around with the canonical now will likely do more harm than good. There aren't any definite negative effects for your SEO by leaving things as they are. As for your question about aggregation, I assume you mean in Google Analytics? No metrics will be aggregated there -- the two pages will appear as separate URLs in your reports. The aggregation that matters for indexation is link equity. When you get links to example.com/page, it will help the rankings of the example.com/category/page URL because that's the canonical version.

Hi there, While I agree with Logan that hreflang may actually be your best bet, in response to those specific questions: Cross-domain canonicals are not inherently problematic. By my understanding, at least, you're free to use rel="canonical" whenever you deem appropriate.

Sorry, I'm confused about the setup. Hosts routinely run multiple sites off of shared IPs, but each domain name resolves as itself. Users and search bots should never see that redirection at all and shouldn't be crawling the IPs. This isn't an SEO issue so much as a setup issue. Likewise, any rel=canonical tags on each site would be tied to that site's specific domain name.

Hi, The very best article that I refer everyone to when looking at internal linking, is here. The theory is that you create a strong, relevant link, but make it suitable and in context with the text where it comes from. -Andy

Thank you all! I have forwarded this to the owner of the page, so now we'll just sit back and see the effects

Hi Francis, They should be different sessions, they could be the same type of device or even the same device used in a different way. There is also a report which will tell you exactly what devices were used, which might be helpful.

Topical relevance (LDA) has been positively correlated as one of the strongest onsite rankings factors (https://moz.com/search-ranking-factors/correlations)  and as a result has been a driving factor behind sites adding additional contextual content.   In my experience, a well ranking site likely has a higher contextual relevance because it has comprehensive content on the topic demonstrating subject matter expertise... As SEOs, we typically mimic those strategies that we know high-ranking sites have implemented in an effort to gain higher rankings ourselves.  For business that aren't subject matter experts, and simply add contextually relevant content, the result isn't often improved rankings for the target keyword (e.g.  iphone 5 coupons), but instead is an increase in the overall traffic to the site as a result of a broader set of long-tail keywords with rankings (get discounted iphone 5, best deal on iphone 5, etc.)

Redirected URLs are generally removed from the index pretty quickly. I just checked and the /solutions URL is not indexed in Google, so you don't need to take additional measures to have that removed. A good practice is to have no redirects in your sitemap. When I run new sitemaps, I use Screaming Frog and the first thing I do is remove everything that isn't a 200 status code. Keeping a clean XML sitemap helps your crawl budget and gets bots to focus on the more important parts of your site rather than having them step through unnecessary steps.

Using the disallow directive in the robots.txt file is probably the better bet as far as making sure that our tools don't crawl those pages and report duplicate page titles. I think the disallow directive is the way to go! That said, I'm not an SEO expert, so it might be worth checking in with a web developer to see if they have different suggestions.

I think you posted this message before seeing my last response, but you'l notice that they use "results" (like us) and google it picking up on that,  but your site has nothing after the number

I think you're doing the right thing by optimizing for the grammatically correct version of the phrase. Google undoubtedly considers the phase without tones a semantic equivalent. If I were you, I'd focus instead on earning more and more authoritative links to the page so I have a better chance of outranking the ones that are optimized for the term without proper tones. If you can, try to get links with link text that excludes the tones.

To be clear - Pagespeed Insights does not measure the speed of a page, It's entirely possible to have a score of 90 and a load time of (a disastrous) 29 seconds. I have screenshots to prove it All Pagespeed does is check for the typical server/software configurations that "usually" lead to faster pages, as Linda mentions. All you should care about is what your VISITORS experience and what they think is "fast enough". You need to put RUM (Real User Monitoring) on the site's pages so you can directly correlate visitor behaviour/conversions to page speed. (And so you'll actually know what speed real users experience, as opposed to the totally synthetic speed tests like Pagespeed Insights or even webpagetest.org/gtmetrix etc.) If the site uses Google Analytics, this RUM is built in, but you must adjust the tracking code snippet to get worthwhile value from it. By default, Analytics will only track 1% of pageviews' speed. Adjusting the tracking snippet will allow tracking of up to 100% of pageviews or 10,000 pageviews per day. You'll have SERIOUS power in your hands when you can see the actual speed performance of all pages that takes into account REAL user variables like connection speed, location, browser, mobile vs. desktop, time of day/server load etc, etc. Don't guess - use data. Hope that helps? Paul P.S. If the site does have really high-volume traffic, you will already have at least a bit of data in the Site Speed report in GA at teh defualt 1% You can use it as a baseline to prompt action and to measure improvements, but you want to get up to that 10,000 pageviews tracked per day as soon as possible.

Hope the below helps. 30x in .HTACCESS #PERMANENT REDIRECT redirect 301 /url-linked-to.html /new-page-you-want-to-link-to.html #TEMPORARY REDIRECT FOR SHORT TERM CHANGES redirect 302 /url-linked-to.html /temporary-page-you-want-to-link-to.html Canonical Tag Cheers Tim