One of my main concerns is about SEO, when I have the intention to completely redesign a website and make it work on a mobile device.
Following that idea, I have been researching on Google Developers and have decided choose the first option "Responsive Design"
CURRENT SITUATION
Made in TABLE
SEO based only in KEYWORDS and DESCRIPTION
URL not friendly
Use the first version HTML
Layout old-fashioned
Excellent position in the GOOGLE Rank
Excellent traffic visitors
TARGET
Create mobile version to attend target group which use mobile device
Full redesign, including best practices organic SEO Friendly URL
HTML5
CCS3
Responsive Design
New technology JSP to PHP (Laravel 4)
OBSERVATION
Because this site has been online since 2002, it has developed an excellent position on GOOGLE. The biggest concern of all, is to lose the position because of the migration to the new version. Im Seeking alternative or more efficient solution, I'v identified the use of 301 redirect to the new URL.
My Questions are as follows:
If the domain of the website is maintained, will this change only the URL?
example:
From
www.website.com/cs/detail.jsp?id=123456
www.website.com/aboutus.html
To
www.website.com./product/detail/123456/lorem-ipsum-dolem-sit-amet
www.website.com/about-us
Following that thought, I'v found some solutions like 301 redirect.
DOUBT 01
I will use the 301 redirect to each page, then will I have to put that 301 redirect one-to-one?
aboutus.html
response.setStatus(301);
response.setHeader( “Location”, “http://www.website.com/about-us” );
response.setHeader( “Connection”, “close” );
cs/detail.jsp
response.setStatus(301);
response.setHeader( “Location”, “http://www.website.com./product/detail/123456/lorem-ipsum-dolem-sit-amet” );
response.setHeader( “Connection”, “close” );
DOUBT 02
Following the doubt above, will i have to put the new website in sub folder?
Example:
|public_html
|-index.html
|-quemsomos.html
|-cs
|--detalhe.jsp
|-novo-site
|--index.php
And will the URL will be just like that of:
www.website.com/new-website/quem-somos
www.website.com/new-website/product/detail/123456/lorem-ipsum-dolem-sit-amet
DOUBT 03
Is there anything else i need to worry about?
Answer 1:
Its better to redirect the entire site using a .htaccess file rather than writing it in every single page. You can refer to my link below that will help you gain an understanding of this redirection.
Answer 2:
The URL strictly follows your directory structure.
Answer 3:
The search engines will take some time to discover the 301, recognize it, and credit the new page with the rankings and trust of its predecessor. This process can be lengthier if search engine spiders rarely visit the given web page, or if the new URL doesn't properly resolve.
You may refer to the link below to gain a better understanding about the 301 redirection.
how to 301 redirect
Related
I have a website that write URLs like this:
mypage.com/post/3453/post-title-name-person
In fact, what is important is the post and ID part (3453). The title I just add for SEO.
I changed some title names recently, but people can still using the old URL to access, because I just get the ID to open the page, so:
mypage.com/post/3453/post-title-name-person
mypage.com/post/3453/name-person
...
Will open the same page.
Is it wrong? Google webmaster tools tells me that I have 8765 duplications pages. So, to try to solve this I am redirecting old title to post/id/current-title but it seems that Google doesn't understand this redirecting and still give me duplications.
Should i redirect to not found if title doesn't match with the actual data base? (But this can be a problem because links that people shared won't open) Or what?
Maybe Google has not processed your redirections yet. It may take several weeks and sometimes several months to process all pages, especially if they are not revisited often. Make sure your redirects are 301 and not 302 (temporary).
That being said, there is a better method than redirections for duplicate pages: the canonical tag. If you can, implement it. There is less risk to mix up redirections.
Google can pick your new URL's only after the implementation of 301 redirection through .htaccess file. You should always need to remember that 301 re-direct should be proper and one to one to the new url. After this implementation you need to fetch those new URL via Google Search console so that Google index those URL's fast.
So I overhauled a complete website the other day and found some of the old pages snippets in the google search results. The old page had an ugly link structure such as domain.com/index.php?article_id=123. The new site uses pretty permalinks such as domain.com/pagetitle.
Is there a piece of code I could put into the .htaccess file in order to redirect all ugly permalinks to the new site?
Edit
Additional info: The old links don't exist anymore. The old site and the new one's structure differs a lot, not all contents from the all site were adapted. Main problem is that I don't want the old links in the google search results to always throw a 404 at the user.
Maybe something of a
RedirectMatch ^/index.php?$ http://www.example.com/somepage
This will redirect all pages starting from index.php to another location
I don't have the rep to comment on the other answer, but that is a very improper solution if you value your SEO at all. A redirect is your way of telling Google "I've got the same page, I just moved it". There's a much better way to do this that won't negatively affect your SEO at all.
You should create some logic to redirect those old links to your new links.
Here's an example of how you could do it:
Go to the beginning of your program, before any logic takes place.
Use code to retrieve the requested page. In this case, you might be able to get away with simply checking for GET variables that match article_id.
If the requested page is a match for your GET variable, run a query to see if the article exists. (Obviously, you'll still want to 404 articles that don't exist).
Retrieve the content used to generate the new, more SEO-friendly URL's. This is probably the article title or something.
Write some code to generate the new article title. At this point, if this is working properly, you should be able to system print that new URL to make sure it's correct.
301 redirect to the new URL. Don't 302 or any other number, 301 redirect it. This lets search engines know it's the same page and content, but it has permanently moved.
I have a website ranking well in Google, my current website has dashes in and looks like so...
this-is-mine.com
Ive just also bought
thisismine.com
I'd like to point the latter to my first site, but I dont want it to be classed as duplicate content.
I'm unsure if I just do this through 123-reg but will this affect my Google rankings, or is there a correct way of doing this without penalising myself?
According to the link below, my thoughts are confirmed.
A 301 is fine as it forwards everything including page rank to the "new" site. In your case this-is-mine.com.
A 302 could/would be a problem for SEO.
http://seo-hacker.com/301-302-redirect-affect-seo/
If your current website is ranking well then don't disturb it. There is no benefits in pointing multiple domains on one website. You can also make a single page website on the new domain and optimize it for Google and link with your old one.
If you still want to do this then do a 301 redirect but make sure that the domain is new and has no spammy back links pointing to it.
I've got a bit of a problem with Google's Change of Address function on the Google Webmaster tools. I hope that I got the right part of the Stack Exchange for this.
Basically, for six years I've been using a blogging platform blogsome.com (which hosts domains like http://site-address.blogsome.com), which is basically a hosted wordpress server. I've had no complaints about it, until they recently announced that they would close down on a very, very short notice.
With this, I found it a good opportunity to set up a domain of my own (let's call it http://site-adress.net for now). Setting up the domain and website went well, but when I went to Google Webmaster Tools to tell it about the change of address, this proved to be surprisingly difficult. In particular, when I tried the "Change of Address"-option on the dashboard, I get the message that this option is not available for subdomains.
What method would there be to correctly tell google that my site has changed? I cannot use 301-redirects, because 1) I do not have access to do that on blogsome, and 2) blogsome will be shutting down really soon (read: within a week; the news was on a very short notice, and I spent most of that time actually setting up the website). I've also read somewhere that you should keep your old site alive for 180 days, and again that is no option for me either.
The best option is to use a .htaccess file (plain text file)
And put this inside it and upload it to your site.
Redirect 301 / http://www.yournewdomain.com/
If you cant do that you might be able to upload a new index.php with the following inside it.
<?php
header( "Status: 301 Moved Permanently" );
header( "Location: http://www.yournewdomain.com/" );
exit(0)
?>
If you cant do that either, then say what you can actually do on the server?
Do you have any actually access to files? Or can you edit the templates?
You should be able to move it in gwt i'm not 100% sure, I never done it with a subdomain or a blog-hosted site. So I might be wrong here.
Add your new domain with the blog to your gwt account and get it verified.
Then in GWT goto your bloghosted site then to Site Configuration > Change of address
And then select your new domain under the "Tell us the URL of your new domain" part and hit Submit
I am rewriting a web application and will be porting procedural PHP code to a framework.
At the same time, the layout of the pages (but not the critical content) is not changing.
I'm thinking that I need to some how port the old URLs by using a 301 Redirect permanent.
Any advice on how to proceed? As this site is long established with a good reputation, it's important we maintain rankings in Bing and Google.
Thanks.
You should use 301 redirects instead, that will carry over the data the engines have for those pages and you should be fine