I am using wordpress to create a website. I have shifted my website to new domain but i have used the backup of old domain name.
now the old domain is not owned by me someone else has booked it. i am trying to apply for google ads but every time i try to apply they reject my request due to bad links.
my previous domain was .com now i have .com.au domain, report shows bad links associated with old domain.
can anyone guide me how to remove these links
Related
This is a peculiar one.
I work for an agency, and we develop WordPress and JAM Stack sites for our clients.
I have been contacted by the IT team for one of the clients (an NGO), and they flagged something that I have not seen before.
NOTE: I am going to be using example.org as the website, to protect the identity of the client.
Basically, we developed a WordPress site for them, which works great and all, but as it turn outs there is a page on the website which points to a totally different website
The example page is as follows
example.org/news/points-to-different-website/
The news page doesn't exist in anywhere on WordPress system, and neither does it exist as a custom post type.
And another thing, I noticed is when I removed the / at the end of the URL, it shows the custom 404 page developed for the website
example.org/news/points-to-different-website
But as soon as you add the /, it shows a totally different website.
I have checked all the Apache configuration files related to the site, and it is just the normal setup for any WordPress site.
So, I am wondering what could be causing this, and how can one prevent it?
That's a strange issue. Does example.org/news/points-to-different-website/ actually redirect to another full URL, i.e. differentwebsite.com, or is the different site actually at example.org/news/points-to-different-website/?
Try
emptying the trash for both pages and posts, as there could be a conflicting slug that is causing a redirect.
Reset permalinks.
Using PHPMyAdmin, search the database for the URL points-to-different-website and see if there is malware or some kind of a redirect, an iFrame, etc.
This can sometimes happen if the server hostname is not set up correctly.
What can happen is website on the server will show in place of a non-existent site or page from another website on the same server.
If you are using a reseller hosting/shared hosting, then the site could be from another account on the server, the site could also be from another server, for example:
There are 2 servers with the hostnames serverone.myserver.com and servertwo.myserver.com... A site on serverone might show in place of a site or page on servertwo.
My website was running just fine then one day i found some other domain was redirecting to my site. whenever someone go for that domain url that redirects to my site.
the problem is the other domain is not even registered. that was registered years ago and that owner had clients on that. but he gave to that domain and domain is free since then. but now a days that is automatically redirecting to mine. whenever my posts update, RSS feed is sent to that domain's client.
the other domain owner has nothing to do with that because he is no longer the owner and can not help.
I tried to update .htacces and defined the rules to not accept that url but instead it always show error that too many redirects because if that domain is restricted it tries again and again due to which my site goes down..
how could i overcome this issue?
Good day 😀
I have a WP Multisite in which a site was running. The administrators decided they would revamp the site, and they did it in a provisional subdirectory so that the original site would be available while the changes took place. So this is the current structure:
mymultisite.com
mysite.com
mymultisite.com/mysitebeingremade
Now that the site changes have been finished, I would like to attach the domain name to the revamped site. So, I try to disable the site currently attached to mysite.com, change its domain to a different one, and attach the domain name to the revamped one. So from the sites configuration I make the following changes in Sites > Edit site > Site info:
mymultisite.com
mysite.com -> mymultisite.com/mysite
mymultisite.com/mysitebeingremade -> mysite.com
But it seems as if the domain name keeps pointing to the old site. What am I doing wrong? Or is it just impossible to reuse a domain name previously used in a multisite, but not in use anymore, for a new site?
I guess that I can just overwrite the original sites with the one with the changes, but I think it is too much hassle for a seemingly simple task.
Thank you 😀
Ok, I sorted it out.
It seems that, when you delete a site from the multisite, it doesn't get deleted from the database. Specifically, one entry remains in the table [prefix]_domain_mapping in which the fields 'id' and 'blog_id' are still pointing to the old site that was linked to that domain.
By changing those two fields to the id of the new site that will be using that domain name, and provided that all the changes have been made to the configuration of that site in the site configuration to use that domain for that site, it should work ok.
Thank you,
I'm a new in web development so the question is maybe pretty simple, but I can't handle it by myself.
I have a wordpress website which hosts on hostmonster.com and it has a URL, let's say, http://aaa.com/bbb.org. So it is located in the subdirectory bbb.org of the main directory http://aaa.com in my host monster account.
I also have a domain name, let's say, http://bbb.org on godaddy.com and now I want to make my site available on address http://bbb.org. How to do that?
I did the following thing. I forwarded http://bbb.org to http://aaa.com/bbb.org in settings on godaddy.com, but it's not what I need, because user still see old address (http://aaa.com/bbb.org) in his address line. So what am I doing wrong?
I think you don't want to redirect from http://aaa.com/bbb.org.If so you will be need 5 step.
STEP 1: TRANSFERRING FILES
The first step in moving your website to your new domain name is to create an account on your server or shared hosting plan for the new domain and then transfer over all of the old website files to the new account you have created for the new domain. Be sure to just copy the files over and do not in any case delete the files from the old account for the old domain name yet.
STEP 2: CHANGE NAMESERVERS
Be sure and change the nameservers of the new domain name to point to the newly created account that you have created on your server or shared hosting plan. Keep in mind that it will typically take between 48 and 72 hours for the DNS to propogate throughout the web.
STEP 3: CHANGE FILES
The next step is to change all instances of the old domain to the new domain within the files that you have transferred over to the new account on your server. You will most likely be able to accomplish this very quickly if you just use the find and replace feature in your FTP client (i.e. Dreamweaver, FileZilla, etc.). Making all of your links absolute links rather than relative links is usually the best way to go for SEO purposes so if this is something that you had ever considered changing over then now would be a good time to go through and audit all of your website files to change relative links to absolute when appropriate.
STEP 4: CREATE 301 REDIRECTS
Setting up 301 redirects in your .htaccess (assuming you have a Linux server) under your old account is very important. A 301 redirect will work to automatically and permanently redirect visitors and search engine bots who visit www.olddomain.com/my-page to www.newdomain.com/my-page. This is very important from an SEO perspective because 301 redirects have the potential to pass through the “link juice” of any backlinks pointing to the old domain to the new domain along with any accompanying search engine rankings. This is also very important from a user perspective because anyone that tries to visit any page on your old domain will be automatically sent to the appropriate page on your new domain. Read this guide on how to set up 301 redirects to get all of the nitty gritty 301 redirect setup details.
STEP 5: TEST
Make sure that your nameservers have been set up on your new domain and that the DNS has finished propogating. Once you verify that the DNS is resolving correctly for the new domain then it is time to test out all of the old pages that you are redirecting from the old domain to the new domain and then also test by looking through each page of the new site and make sure that there are no errors (from find and replace errors when changing files or other issues).
If all of the pages of your old site have been indexed by Google then a quick way to test out that the 301 redirects have all been set up and working properly is to simply do an advanced Google search query that will return all of the pages from your old site indexed by Google. You can do this simply by typing “site:olddomain.com” into Google (without the “”). Now all you have to do is click on every page and if you have set up the 301 redirects properly then each time you click on the page link your server should automatically and instantly redirect you to the appropriate new page on your new domain.
That all you need ?
Typically, a hosting solution will have DNS redirecting that it will help you. The issue is that you might be using GoDaddy for your DNS managing. In which cause the redirecting DNS with hostmonster will not come through.
The best thing to do is have your GoDaddy point to the nameservers from HostMonster and have HostMonster control DNS. Then you can just create a redirect inside HostMonster and point bb.org it to http://aaa.com/bbb.org but your URL will just be bbb.org.
This sounds like a Masking problem, (you have enabled forwarding, but not masking) http://support.godaddy.com/help/article/422/forwarding-or-masking-your-domain-name
Also, note that you 301 redirects will be cached by clients, so use 302 redirects unless you are sure you've set it up the way you want it.
Make sure to follow the above answers. But using the The Duplicator plugin will streamline the actual Wordpress website migration very easily.
Please can someone help me to clarify what issues i might have when the hosting company changes the DNS settings to point away for the current old site (basic html) and to the new WordPress version of the web site?
Both sites are with the same hosting company (I cannot change hosts or hosting names now, my client and the hosting company are long term business partners). I think the server that the current live website is unable to host WordPress. So they set up another server for WordPress and called it something completely different.
Old website address http://www.therealwebsitename.co.uk
Current Location of new WordPress site on hosting server: http://test.blahsystems.co.uk
I think this bit is important!!
The new website is on a Windows Server and uses pretty perma links and also the .html pages plugin. There are also some redirects going to 7 pages on the old site. Everything is currently working ok.
Nest week the hosting company are going to change the DNS settings to point to the new website http://test.blahsystems.co.uk which will hopefully become the new website with the new address of http://www.therealwebsitename.co.uk
The hosting company have also said that I should not have used Permalinks at the moment because once the DNS is pointed to the new site the links will have become permanent (well I had already set up permalinks before they told me). I have not used the full address when making any links within the site.
Will the 'Find & Replace' plug-in on the database still work ok to make any required changes? I am confused as to how the DNS change actually works, will this affect what the links are called in the database or can I still change them from:
http://test.blahsystems.co.uk
to
http://www.therealwebsitename.co.uk
I presume I will need to change the Word Press address and site address in the settings panel to http://www.therealwebsitename.co.uk, once the DNS propagation has finished.
Very long winded I know but any help would be much appreciated.
Thanks
Ok - I will do the best I can to answer these 8-)
Please can someone help me to clarify what issues i might have when
the hosting company changes the DNS settings to point away for the
current old site (basic html) and to the new WordPress version of the
web site?
When you change your DNS - it's like moving into a new house.
The whole building can change - so it sounds like you're leaving a Windows environment for a Linux environment. Which is cool.
What happened on the old site - should not really impact the new site OTHER than the fact that search engines will still try to remember the old sites structure. It will take time for the search engine to realize that things have changed and that pages are new or missing.
301 Redirection can help with this.
Both sites are with the same hosting company (I cannot change hosts or
hosting names now, my client and the hosting company are long term
business partners). I think the server that the current live website
is unable to host WordPress. So they set up another server for
WordPress and called it something completely different.
Old website address http://www.therealwebsitename.co.uk Current
Location of new WordPress site on hosting server:
http://test.blahsystems.co.uk
I think this bit is important!! The new website is on a Windows Server
and uses pretty perma links and also the .html pages plugin. There are
also some redirects going to 7 pages on the old site. Everything is
currently working ok.
WordPress can use permalinks. If you have moved pages around - like mysite.com/about-us and it's not called mysite.com/about - you will need to create a 301 Redirect to let search engines know.
Nest week the hosting company are going to change the DNS settings to
point to the new website http://test.blahsystems.co.uk which will
hopefully become the new website with the new address of
http://www.therealwebsitename.co.uk
The hosting company have also said that I should not have used
Permalinks at the moment because once the DNS is pointed to the new
site the links will have become permanent (well I had already set up
permalinks before they told me). I have not used the full address when
making any links within the site.
I don't think using permalinks will cause a problem. They aren't "permanent". Nothing is - it's all in a transient state.
Will the 'Find & Replace' plug-in on the database still work ok to
make any required changes? I am confused as to how the DNS change
actually works, will this affect what the links are called in the
database or can I still change them from:
http://test.blahsystems.co.uk to http://www.therealwebsitename.co.uk
Sounds like this plugin is outside of the WordPress install? If so - it should still work.
If it's a plugin your hosting provider is giving you, then there should be no problems.
I presume I will need to change the Word Press address and site
address in the settings panel to http://www.therealwebsitename.co.uk,
once the DNS propagation has finished.
Yes, make sure to update your General Settings prior to the site going live so you don't have any down time.