My SEO tool is telling me that https://example.com has duplicate content with those pages.
URL(s) with Duplicate Page Titles
https://example.com/Employment/default.aspx
https://example.com/employment/Default.aspx
https://example.com/Employment/Default.aspx
i have IIS6 and i used a rewrite lowercase rule to solve this, the problem is solved on the browser and all URLS are lowercase now but i still have duplicate pages and my SEO tool is still showing the duplicates
i want to write a rule on IIS to get rid of those duplicates
PS: https://example.com is the same page as https://example.com/Employment/Default.aspx
Assuming the content on all pages is the same and this is, in fact, the same page (with different URLs), then rel=canonical is your best bet. This will tell Googlebot (and Bing, etc) that Default.aspx is really the same as default.aspx, and to attribute any search relevancy you receive with Default.aspx to default.aspx.
On proper canonical tags here:
https://support.google.com/webmasters/answer/139066?hl=en
Alternatively (and perhaps to be used in conjunction with), there are 301 permanent redirects.
This accomplishes effectively the same as the canonical, but permanently redirects visitors from Default.aspx to default.aspx, Googlebot included. Again, search relevancy will be passed from the former to the latter link.
More on implementing below:
http://www.iis.net/configreference/system.webserver/httpredirect
Related
I'm trying to redirect a page and any subpages to the root but I can't find a way of doing it. I'm using the redirection plugin (https://redirection.me/). I would rather doing it via the plugin to keep all redirects in one place rather than .htaccess.
I would like to redirect https://www.example.co.uk/developments/ and any subpages e.g. https://www.example.co.uk/developments/test or https://www.example.co.uk/developments/another-test etc. to the home page.
I tried just now it seemed to break the subpages so I had to revert the redirect.
This is what I was trying to use in the source URL:
/developments/development-name/*
And the target URL:
/
With REGEX and Ignore Slashes enabled.
/developments/development-name/* is not what you want. It looks like you are trying to do globbing with that *. In regex, the equivalent of a glob * is .* where . means "any character" and .* means zero or more of any character.
The rule that would implement a redirect to the home page is:
source: /developments/.*
target: /
However, redirecting to the home page is not usually a good idea. It is usually better to remove the content and show a custom 410 Gone error saying why the content was removed. When you redirect to the home page:
Users don't get a meaningful error message and get frustrated with the bad user experience
Search engines call it a "soft 404" error and treat it just like the content was removed, so you don't get any SEO benefit.
My problem is that my client has migrated from Wordpress to Shopify, and there were some important pages on the site under the /services/ folder. I wanted to redirect them to their new pages after the migration, which are /pages/ pages.
Shopify has reserved /services/ URLs, however. Therefore I cannot redirect mydomain.com/services/some-services-page to mydomain.com/pages/some-services-page.
Additionally, I cannot change the URLs of the /pages/ pages to /services/ pages.
What would be the next best step here? It seems like a significant limitation of Shopify, as any pages you want to migrate from another CMS that have /services/, apparently can't be redirected, and you lose the SEO value. Those pages are now returning 404 and there doesn't seem to be anything I can do about it, or am I missing something?
I've had some back and forth with Shopify support, which ultimately ends with them saying its a limitation of Shopify and I should submit a feature request. I appreciate any advice you might have.
You can manually create redirects from old relative urls to new ones on shopify by going to [yourstore].myshopify.com/admin/redirects
If you want to track which pages customers are exactly hitting and getting 404's, you can use app Transportr:
https://apps.shopify.com/transportr
It tracks which pages are getting 404, and you can also create redirects directly from an app
I recently migrated a client's e-commerce site from Ecwid to WooCommerce. Ecwid's URL's use fragment identifiers which is now a problem as I can't set up a 301 redirect to the new URL using .htaccess. As I understand, everything past the # isn't accessible to .htaccess.
I'd like to try and preserve their SEO ranking as well as easily update all the old URLs to new.
There are dozens of Wordpress plugins which offer the ability to redirect pages, but I'm concerned I'll have the same issue. From what I've read Javascript redirects don't use the 301 response code, so search engines wouldn't know what the new URL is.
Is there any other way to redirect this:
example.com/products/#!/100-Cotton-Sash-Cord/p/19877065/category=4619310
to this?
example.com/shop/all-natural/100-cotton-sash-cord/
As you mentioned, everything after the # isn't processed by the server.
However, if your old site was previously indexed completely by Google, you can presumably pick the "ugly" URLs for the snapshot pages and redirect those?
Is it ok to have custom Permalink Settings in wordpress of http://www.sitename.com/sample-post instead of http://www.sitename.com/sample-post/. Is it ok with search engine.
ie, /%postname% instead of /%postname%/
From Search Engine point of view the URLs with or without slash are two different identities and neither is preferred. From users point of view, we should have only one URL to avoid any confusion and better user experience. From SEO point of view, the preferred version should return 200 and the duplicate URL should 301 to the preferred URL
Matt Cutts (head of Google’s Webspam team) prefer trailing slash.
http://www.mattcutts.com/blog/seo-advice-url-canonicalization/
You can also read more from here:
When should I use a trailing slash in my URL?
http://googlewebmastercentral.blogspot.sg/2010/04/to-slash-or-not-to-slash.html
Here is the situation: I took over a WordPress project, which turned out to have a corrupted database (wp_terms table missing among other problems) for a while. While all posts appeared to be assigned to a category, they actually weren't!
Result: A ton of 404s we're created because url/category/something/post-slug was actually only accesible via url/post-slug. Ouch!
There were a lot of content changes in the past and after the SEO company discovered the 404s (after months), they ask me to set 301s for all posts.
I have now completely rebuild the database locally, imported posts/pages etc. and would like to assign the posts back to its categories. What's the best way to do so? I assume I cannot simply remove the permanent redirects because Google probably has indexed the pages already!?
Should I basically set permanent redirects for the permanent redirects?
For some reason I cannot believe its best practice but lets see what you guys think!
Its really bad practice to use chains of 301 redirects, but sure it kind of happens some times. If you want you can try the other way around and use the canonical option or 302 redirects so if you need to do another redirect in the future not to bug the chain with a third level of 301 redirect. Here is a post that compares the two ways :
Site Performance: rel=canonical vs redirect 301