13

Yes - altering a HOSTS file locally to redirect a domain to an IP isn't the same as simply typing in that IP into the browser. The reason why is that in shared hosting, one IP address houses multiple domains. When you type in that IP address of "your" site (which is also the IP of other sites as well), the server can either a) Give an error b/c it doesn't ...


7

Don't over-optimize. Make sure the pages all have unique page titles and descriptions. Make sure the title attributes (not to be confused with the <title> tag) don't just replicate what the text link says. Make sure the pages load as fast or faster, accessibility doesn't get worse, you use a XML sitemap... Also a good idea to do a full analysis of ...


6

If your wordpress.com blog uses a subdomain such as "example.wordpress.com" You would need to: Set up Google Webmaster tools for your wordpress.com blog (here's how). Set up your new self-hosted WordPress blog to use exactly the same permalink structure as the wordpress.com blog (don't worry, we'll fix this in a minute!). Export your content from the ...


5

If you are changing page URLs and especially domain, be prepared to have a transition period during which the website will probably LOSE visits. Google is going to reprocess your entire site (even if you used 301 redirects), and it might take some time. If your customer looks at visits statistics you better warn him, because he might see a fast downturn in ...


5

If you're already 301 redirecting HTTP traffic to HTTPS then you've got the biggest step already done. Any links to HTTP pages will get redirected to the relevant HTTPS page, and search engines will follow those the same as real users. As long as your sitemap refers to the HTTPS version as well you should be fine. As for more niggly bits, I'd also suggest ...


5

Any used framework under the hood has no effect on the SEO. What it matters SEO wise is the front-end (on Site SEO), and the off-site SEO. Generally any structural, mark-up, content changes have their own effect on SEO. Such changes can be done even with no underlying technology change. For sure changing framework can't affect off-Site SEO. For on-site, if ...


4

The technique you're looking for is called responsive design, utilizing CSS3, this approach allows the content layout and text sizing to change according to the user's browser window size or the screen resolution of their chosen device. Here are a few resources/links/ideas:- CSS Tricks is a great example of responsive design in action SpeckyBoy magazine ...


4

If the HTML is different that will affect rankings as semantic markup definitely play sa ranking in the search engine's ranking algorithm. 301 redirects don't carry over all of the current pages' links value. A small percentage is lost. It takes a while for the 301 redirects to kick in. One or more of these factors can account for the rankings change.


4

If you are using Wordpress now, and simply trying to redirect old Joomla urls to your new urls I suggest using a plugin to make your life easier. I recommend this plugin a lot: http://wordpress.org/extend/plugins/redirection/ Also keep in mind that you should use fancy permalinks within Wordpress instead of the standard ID numbers. You can find this ...


4

Your regular expression has the following problems: It only has .* for the "site" and "sectionname", but is missing one for the "categoryname". Based on your example, there should be a third directory level in your regex. You have parenthesis around items which you don't need to reference, but no parenthesis around the ID, which you will need to reference. ...


4

In WHM (v11.46) there is an option under Home » Transfers » Transfer Tool (in older version it was Copy an Account From Another Account). Here, under Advanced option, choose Remote Server Type: Parallel Plesk and fill up the other required data and submit it. cPanel Migration Team also provide Free Migration Service. Check out cPanel.net :: Migration ...


4

cPanel can do this by going to the following url: http://[ip-address]/~[cPanel-username]


4

I would very much like to use wildcard redirects where possible (like in the directory structure that contains 2,000 MP3 files). If your server software is apache, then you can use the rewrite module to redirect some URLs to others using wildcard character sequences in the regex. For example, to redirect http://example.com/apple1, http://example.com/appleA, ...


4

The short answer is yes. Adding the domain name and IP to your HOSTS file will resolve the domain, locally, to the IP you have entered. When you then visit that domain in your web browser, along with your request to the web server (at that IP address you entered), your browser will send the domain name you have requested. The shared web server will then use ...


3

A sitemap may help with indexing your new URL structure, but remember Google makes no promises they'll crawl or index everything in there at all. However, even if they did index everything in your sitemap, that would not magically make your crawl errors go away. 404(not found) errors explicitly allow for the possibility that the URL may be available again ...


3

It sounds like you've checked off the basic best practices: using 301 redirects and updating your XML Sitemap. The 301s are the crucial bit where preserving rankings is concerned, since Google will recognise the permanent nature of the redirection and transfer PageRank etc. Google's support pages on site migration cover this and some other areas of good ...


3

No, don't copy the tables - that schema has changed quite a bit. You can install the free JUpgrade extension, which will download and install a 2.5 into a subfolder of your website and populate the new DB with your content, categories, users, etc. It can also handle some 3rd party extensions like Community Builder, Virtuemart and Kunena. That's the official ...


3

404s have no effect on PageRank per se, as PR is just a calculation of how many links are incoming to that page. However, 404s will have a small effect on the PageRank of the other pages on your site, as they will now have fewer links pointing to them. Since you have thousands of pages and sound like an established site, this effect will be negligible. ...


3

A quick look at the web host you currently use shows that they only offer 2 hosting packages that are both less than $10/month. This is pretty much guaranteed to be shared hosting as VPS starts at at least $20/month on the extreme low end. So that means you probably don't have root access. That said, there's no reason the other host would need root access ...


3

The tell Google you've moved feature is designed for old domain to new domain and does not support sub domains, sub folders or new domains with sub folders, it is strictly from domain to domain. This question has been asked various times on many forums across the internet, Google does not treat a domain to sub domain or folder a site move. You should ...


3

This is not a Blogger problem: Your blog always has a blogspot addresss www.yourblog.blogspot.com. When you publish to a custom domain, Blogger handles the re-direction from www.yourblog.blogspot.com to www.yourcustomdomain.com for you - and every single post/page is redirected correctly. Now to move from oldcustomdomain.com to www.newcustomdomain.com, ...


3

For example, do I need to worry about the MySQL databases themselves being compromised? Or if I manually move them would they be ok? Yes, you absolutely have to worry about the MySQL being compromised along with just about everything else. The best thing to do here is move as little as humanly possible to preserve the content. Plugins, themes, etc should ...


3

This will vary depending on the Cpanel License, if its not a WHM unlimited license then these are the steps you need to take: Login to Cpanel Click sub domains under category 'domains' Add a sub domain oldsite with root of /oldsite/ Copy all /public_html/ or www depending on how cpanel was setup to oldsite If the domain already has the name servers set to ...


3

it seems to me, the archiving procedure lets the tarball grow and if the tarball becomes (together with all other data) bigger then the available place in your booked hosting, the server kills the process. You will be forced firstly to download all of your data, and archive them locally. Could it be true?


3

You should submit the HTTPS sitemap to the HTTPS property. If your URLs are of the form https://www.example.com/path/to/file then that would be the https://www.example.com property. The fact that you have both properties verified in GSC (formerly GWT) you might get away with it. (The sitemap protocol does not permit both HTTP and HTTPS URLs in the same ...


3

Well, to determine the "best" answer, I'd want to know if you plan to bring back the blog posts that have not been migrated or if they are permanently removed from your website. If they are permanently removed from the site, then the approach you've taken is an acceptable route. If there is a lot of traffic to some of those posts you've removed, it might ...


3

Propagation times are controlled by the time to live (TTL) that is set on the DNS record. The only way to get DNS changes live faster is to have a shorter TTL specified. GoDaddy may be offering to set a short TTL for you, but there is no reason that a short TTL can't be specified at most DNS hosts. Default TTL values vary widely between DNS hosts. ...


3

To make the transition as seamless as possible, redirect each page from the old B site url, to its new location in the new A site url.


3

install certificate for the main domain and all subdomains make site accessible with https, check all subdomain combinations change all internal links in the whole codebase to https check twice, whether all internal links are indeed https now, inclusive static assets like images, pdfs etc. establish redirects 301 from http to https, better based on port (...


3

Google deals with HTTPS redirection absolutely fine and maintaining the ranking. Generally, when you move to HTTPS, you may not notice a ranking drop at all. In some cases even if there will be a drop then it will be a temporary only. Just ensure to do proper 301 redirect of your entire blog pages from http version to https. Also, once you move, make sure ...


Only top voted, non community-wiki answers of a minimum length are eligible