How to add Each Domain A Page in Wordpress

Serves a specific page or post from WordPress depending on the domain used to access your WordPress site. Wordpress Tutorial

Noted That:

To install correctly this each-domain-a-page.zip .
Fisrt Download the each-domain-a-page.zip to your computer
Extract/Open each-domain-a-page.zip to Your Computer.
Then, Find readme.txt file inside each-domain-a-page.zip and Open readme.txt .
Now, Read the Requirements of this plugin. Which Wordpress Version and PHP Version are required to run this Plugin in Your Wordpress Site.
Then, Follow the Tips Below.

Start the Tips:

1. First Download " each-domain-a-page.zip " Plugin to your Local Computer. (Click Download)

2. Then, Login to your " yourdomain.com/wp-admin " Dashboard.

3. Then, Click on " Plugins " + " Add New " from left sidemenu of Dashboard.

4. Now, Click on "Upload Plugin" button.

5. Now, Browse " each-domain-a-page.zip " Downloaded plugin from your computer, Where you downloaded each-domain-a-page.zip According to Step – 1 Above then, click on " Install Now"

6. Now, Click on " Active Plugin"

7. Then, See left sidemenu. " Each Domain a Page " folder is added on left sidemenu. Now, Click on " Each Domain a Page " folder.

Noted that: If you do not see " Each Domain a Page " folder on left sidemenu then, see at left sidemenu " Settings " or " Tools ".

8. Now you configure yourself oR Watch video tutorial below about Each Domain a Page Configurtions and Settings or How to work " Each Domain a Page " in your WordPress site.

After Activated Plugin According to Step-6 then,

Go to " Plugins " + " Installed Plugin " from Wordpress Admin Panel Leftside Menu.
or Direct go to: https://yourdomain/wp-admin/plugins.php
Then, Find " Each Domain a Page " Activated Plugin from Plugin List.
Then, Click on " Settings " from Plugin that is Each Domain a Page
Now, Edit/Add/Config the setting and Click on " Save Changes " button,

Guide

Guide
Install the plugin by clicking ‘Install now’ below, or the ‘Download’ button, and put the each-domain-a-page folder in your plugins folder. Don’t forget to activate it. During activation the plugin attempts to add a few lines to your .htaccess, for compatibility reasons with webfonts. These lines will still be there after you remove the plugin. You may remove the lines (clearly marked with #ruigehond007) yourself at any time of course. If this failed the plugin will warn you, but function properly nonetheless. If you notice webfonts are not loading for the extra domains you might want to add the lines yourself. The lines are at the bottom of this page. Example of setting up the plugin: Suppose you have a WordPress website ‘my-website.com’ on ip address 12.34.56.789, and you want a landing page for ‘www.example.com’ adjust the DNS A records of your domain ‘www.example.com’ to point to the same ip-address as your main domain, 12.34.56.789 in this example in your hosting environment the extra domain must point to the WordPress directory, this is called domain alias, virtual hosting, domain mapping, multidomain or something similar create a page or post with a slug ‘example-com’ If your WordPress sits in the root of your main domain, you are done. Visit your ‘www.example.com’ domain to see it work. WordPress is installed in a subfolder If your WordPress is installed in a subfolder of your main website (as with my own blog joerivanveen.com/blog) it only works when the domain is accessed without path (www.example.com), but will give an error when a user tries to reach www.example.com/path-to-something. This is because WordPress redirects to the path it is installed in (in this case: /blog/blog), which doesn’t exist, so it goes back into a loop. So make sure the subfolder exists and put an index.php in it that redirects back to the domain without the path. So if your blog is in my-site.com/news, you have to create a subfolder ‘news’ in your subfolder ‘news’: my-site.com/news/news and put the index.php in that second deepest folder: my-site.com/news/news/index.php This is the contents of the index.php file: (replace https:// with http:// if you don’t use ssl) You only have to do this once of course, it works for all domains that you point at this installation. Canonicals? Standard, pages will identify with the main site url and their own slug (and permalink structure). You can see that in the head of the page in the canonical and og:url properties. Some SEO plugins let you specify another ‘canonical’ for a page. This may be a good option for you to use. Alternatively, you can check the ‘canonicals’ option of each-domain-a-page. It will attempt to return the domain for the landing page / post everywhere within WordPress. This has the added benefit that users will be sent to that domain when they click on the link for your landing page. I have tested the ‘canonicals’ functionality on several installations and it works consistently there. Please let me know if this does not work in your installation. Locales? If you need (some of the) landing pages to use a different locale, you can specify that in the settings. This will (re)load all translation files that are available in that locale. If you use this it is best to have the default locale of your installation set to ‘English (United States)’ to avoid reloading all the files. For instance my wordpresscoder.nl site is in Dutch, while the rest of my site is in English (United States). I have added one row to the ‘locales’ textarea: wordpresscoder-nl = nl_NL. Leave this textarea empty if you don’t need it, it will not affect your installation at all then. htaccess In case the plugin was not able to update your .htaccess, these are the lines for your .htaccess to make webfonts function properly, you can add them right after ‘#END WordPress’: # BEGIN ruigehond007 Header set Access-Control-Allow-Origin "*" # END ruigehond007 Contact me if you have any questions.

Install the plugin by clicking ‘Install now’ below, or the ‘Download’ button, and put the each-domain-a-page folder in your plugins folder. Don’t forget to activate it.

During activation the plugin attempts to add a few lines to your .htaccess, for compatibility reasons with webfonts. These lines will still be there after you remove the plugin. You may remove the lines (clearly marked with #ruigehond007) yourself at any time of course.

If this failed the plugin will warn you, but function properly nonetheless. If you notice webfonts are not loading for the extra domains you might want to add the lines yourself. The lines are at the bottom of this page.

Example of setting up the plugin:

Suppose you have a WordPress website ‘my-website.com’ on ip address 12.34.56.789, and you want a landing page for ‘www.example.com’

adjust the DNS A records of your domain ‘www.example.com’ to point to the same ip-address as your main domain, 12.34.56.789 in this example
in your hosting environment the extra domain must point to the WordPress directory, this is called domain alias, virtual hosting, domain mapping, multidomain or something similar
create a page or post with a slug ‘example-com’

If your WordPress sits in the root of your main domain, you are done. Visit your ‘www.example.com’ domain to see it work.

WordPress is installed in a subfolder

If your WordPress is installed in a subfolder of your main website (as with my own blog joerivanveen.com/blog) it only works when the domain is accessed without path (www.example.com), but will give an error when a user tries to reach www.example.com/path-to-something. This is because WordPress redirects to the path it is installed in (in this case: /blog/blog), which doesn’t exist, so it goes back into a loop. So make sure the subfolder exists and put an index.php in it that redirects back to the domain without the path.

So if your blog is in my-site.com/news, you have to create a subfolder ‘news’ in your subfolder ‘news’: my-site.com/news/news and put the index.php in that second deepest folder: my-site.com/news/news/index.php

This is the contents of the index.php file:



(replace https:// with http:// if you don’t use ssl)

You only have to do this once of course, it works for all domains that you point at this installation.

Canonicals?

Standard, pages will identify with the main site url and their own slug (and permalink structure). You can see that in the head of the page in the canonical and og:url properties.

Some SEO plugins let you specify another ‘canonical’ for a page. This may be a good option for you to use.

Alternatively, you can check the ‘canonicals’ option of each-domain-a-page. It will attempt to return the domain for the landing page / post everywhere within WordPress. This has the added benefit that users will be sent to that domain when they click on the link for your landing page.

I have tested the ‘canonicals’ functionality on several installations and it works consistently there. Please let me know if this does not work in your installation.

Locales?

If you need (some of the) landing pages to use a different locale, you can specify that in the settings. This will (re)load all translation files that are available in that locale. If you use this it is best to have the default locale of your installation set to ‘English (United States)’ to avoid reloading all the files.

For instance my wordpresscoder.nl site is in Dutch, while the rest of my site is in English (United States). I have added one row to the ‘locales’ textarea: wordpresscoder-nl = nl_NL. Leave this textarea empty if you don’t need it, it will not affect your installation at all then.

htaccess

In case the plugin was not able to update your .htaccess, these are the lines for your .htaccess to make webfonts function properly, you can add them right after ‘#END WordPress’:

# BEGIN ruigehond007

Header set Access-Control-Allow-Origin "*"

# END ruigehond007


Contact me if you have any questions.

serves , specific , page , post , depending , domain , used , access , site , tutorial ,

Name
How to add Tiny Style in Wordpress
How to add Hosting Bandwidth Calculator in Wordpress
How to add Attendance in Wordpress
How to add Post Country in Wordpress
How to add Secure Captcha in Wordpress

Read Article
https://develop.horje.com/learn/1434/reference