This Knowledge Base article will guide you through the installation of Wagtail.

If you aren’t familiar with Wagtail, check out it’s official documentation by clicking here.

Let’s begin!

How to Install Wagtail on Shared Hosting without Root

Step 1: Login to your cPanel. There’s a lot of ways to do this, but the sure-fire easiest way is to log in to your Client Area, then open your cPanel.

Step 2: Once your cPanel is open, scroll down to the Software section and open the Setup Python App link.

Step 3: Once the Python app opens, click Create Application in the top right corner.

Step 4: You will be presented with a blank Application setup screen, much like the one below:

1. In Python Version, select the version to use in the virtual Python environment. As of this writing, Wagtail requires Python version 3.7.10, so be sure to choose that version.
2. In Application Root, enter the name of the folder associated to your domain that will be used to store the files of the web app.
3. For application URL, choose the domain or subdomain to use for the application. You can also append a URL location, like /wagtail, if you wish.
4. Leave the Application Startup File and Application Entry Point fields blank. They will be auto-populated.
5. In the Passenger log file, enter the name and path to the Phusion Passenger log file. You will be creating this path here, it doesn’t have to already exist.
6. There are no environment variables to add.

Once you’ve filled in the required fields, the screen should look like this:

Click Create in the top right corner to create the environment.

Step 5: Your web app will now be listed in the Web Applications list.

Next, we need to obtain the line of code to activate the application. To do this, click the pencil icon next to your App:

The Application “Editor” allows you to perform some key functions for your Python app, so let’s take a look at those real quick so you are aware:

1. At the top of the page is the option to destroy this application, cancel, or save any changes you made.
2. The Restart and Stop App settings allow you to do as they say – Restart your app or Stop the app.
3. The text at the top is the command line code you will use in the coming step to activate and enter the virtual environment for this Python app.
4. The main settings allow you to control the following:
   1. Python Version
   2. Application root directory
   3. Application URL
   4. Application startup file
   5. Application Entry Point
   6. Passenger Log File

To proceed to the next step, we need to copy the command at the top of the page to our clipboard.

To do this, single-click the text. The ‘code’ is written on the page in such a way that a single click anywhere in the command that has a purple background will automatically be copied to your clipboard.

Step 6: Now, return to the cPanel Home Screen by clicking the 9 squared-square in the top left corner.

Once on the home screen of cPanel, scroll down to the Advanced section and click the Terminal app.

You will see a warning screen like the one below. Click I understand and want to proceed to continue.

Step 7: The terminal will be open and you will be taken to your prompt:

Using your mouse, right-click in the black space of the terminal and choose paste to paste the command you copied earlier from the Python app:

Once you’ve pasted in the test, press the enter/return key on your keyboard to run the command. Your Terminal Prompt should look similar to mine (below) after running the command.

Note on the new line, before my cPanel username is (wagtail:3.8). This indicates I’m now in the wagtail environment.

Step 8: Next you need to change the directory (cd) into the directory where your wagtail directory is located.

Let’s break down what you see in the image above, as many people aren’t really comfortable with the command line (Terminal):

1. First I used the cd command to change directories into the directory where my wagtail directory is located. This command is cd /home2/mycpanelusername
2. Following that I used the ls command to list the files/folders in the directory /home2/cchostingdemos. The output of that is what you see in a few different colors and as you can see, the wagtail directory is listed.
3. Next, I used the cd command again to change directories into the wagtail directory.
4. As you can see in the end, I am now in the wagtail directory.

Step 9: Now we need to upgrade pip. PIP is the package manager for Python. If you are familiar with apt or yum on Linux, it’s very similar.

To do this, type the following command in your Terminal then press return/enter on your keyboard to execute the command.

pip install --upgrade pip

Your Terminal should run a couple of commands, then send you back to prompt. It should look like this, or very very similar:

As long as you see a message like this:

Successfully installed pip-(version number here) and you are sent back to a ready prompt, you’re good to go!

Step 10: Next you need to install Wagtail. To do this, run the following command in your Terminal prompt:

pip install wagtail

Your prompt should look like this when done:

Congrats, now you’ve installed Wagtail!

Step 11: Next, you need to create a project. To do this, use the following command in your terminal:

wagtail start project

Except replace the word project with the name of your Wagtail project.

Your terminal output should look similar to the output below:

Perfect, my project called project3, has been created.

Step 12: Next, you need to navigate to the project folder and run migrations. To do this, run the following command:

cd project3 (replace project3 with the name of your project)

Followed by this command:

python manage.py migrate

I won’t paste the entire output here because it’s too long, however, before pressing enter/return on your keyboard to run the above command, your terminal should look like this:

When the migration is finished, you will be returned to a blank prompt:

Step 13: Next you need to create a superuser to login to the admin of Wagtail.

Using the Terminal, run the following command:

python manage.py createsuperuser

First, you will need to create a username:

(wagtail:3.8)[cchostingdemos@rs2-dal project3]$ python manage.py createsuperuser
Username (leave blank to use 'cchostingdemos'):

Following this you will need to enter an email address:

(wagtail:3.8)[cchostingdemos@rs2-dal project3]$ python manage.py createsuperuser
Username (leave blank to use 'cchostingdemos'):
Email address:

And lastly, you’ll need to give this superuser account a secure password.

You will be prompted to re-enter the password a second time to ensure it matches, and after that the superuser will be created. Your terminal will look similar to this:

Step 14: Now you need to test that you can access your app. My app was installed at https://wagtail.cchostingdemos.com, so when I visit that in my browser, I see the following:

Congrats, that means your app is setup properly. Now we need to configure some other settings.

We’ll be using a command line text editor called nano to make these final changes, so pay attention to the steps below very carefully.

Step 15: In your terminal, type the following command, then press enter/return on your keyboard:

Next, type the following command, then press return:

Nano will open and it will look like the screenshot below:

Nano is a command line text editor. You’ll be using your up and down arrow keys to move to the lines we need to access.

Use your down arrow key to position your cursor below the line that says:

sys.path.insert(0, os.path.dirname(__file__))

Your terminal window should look like this once your cursor is positioned properly:

On the line where your cursors is, enter the following text:

sys.path.insert(0, ‘project’)

Except replace ‘project’ with the name of your wagtail project.

When entered, your command line window should look like this:

Step 16: Next, you need to move your cursor down 2 lines to the line where def application(environ, start_response): is printed and delete all of the text. You will be deleting the text highlighted in the screenshot below:

To delete, hold down the Delete key on your keyboard at the start of the line. All of the other lines will collapse into the start of the line and be deleted. It will look like the gif below while the text is being deleted:

Step 17: Now that you have deleted the extraneous text, you will want to enter the following text:

import project.wsgi (where project is the name of your wagtail project)
application = project.wsgi.application (where project is again, the name of your wagtail project)

The text should look like this when entered into the terminal window:

Now you are ready to exit Nano and save your changes to this file.

To exit nano, you need to push Control X on your keyboard. This is the exit command. Your command line window will look like this after pressing that keystroke combination:

Notice at the bottom, you are being prompted to save your file.

Push Y on your keyboard to save.

After pressing Y, nano will ask you to enter the name of your file. It will look like this:

As you are not changing the name of the file, only the contents within the file, press enter/return on your keyboard to use the existing name.

You will be returned to a blank prompt, and if all went well, your command line window will look like this:

Step 18: And we’re almost done, you just need to return to your cPanel and open the “Setup Python App” section again:

Once the list of Python apps loads, click the circle-arrow icon to restart your Python app.

And now you’re done!

To admin your app or login, visit https://yourappname.yourdomain.tld/admin and login using the SuperUser credentials you created in the earlier steps!

Congrats, that’s how to install Wagtail at ChemiCloud!

We hope you found this tutorial helpful! Let us know in the comments.

In this Knowledge Base article, we will cover how you can easily add someone to your GoDaddy account.

How to Delegate Access to Your GoDaddy Account

Step 1: Click here to open the GoDaddy login page. After it opens in your browser, go ahead and log in.

Step 2: After logging in, hover over the Account Settings and in the menu that appears click Delegate Access.

Step 3: GoDaddy will likely ask you to login again to ensure you are who you say you are. After this, you will be taken to the Delegate Access screen.

On this screen, look for the “People who can access my account” section and click “Invite to access”.

Step 4: The Invite to Access modal will appear where you have these options:

• Enter the name of the person you wish to invite to access your account.
• Enter the email address of the person you wish to invite to access your account.
• And you can delegate the access they have. For example, you can choose:
  • Products, Domains, and Purchases. Access to manage products, domains, and purchase products using credit cards stored in the profile. No access to view or modify the payment information.
  • Products & Domains. Access to manage products (e.g. hosting) and domains only.
  • Domains only. Access to manage specific domains only. Choose individual domains under My Domains.

Choose the appropriate access level, then click the Invite button to dispatch an invitation to that person.

Looking for a GoDaddy alternative? Join the growing club of happy customers who made the switch to better, faster web hosting!

After clicking Invite, an email will be sent to the addressed individual, and they will be allowed to create a GoDaddy account if they do not already have one. Your Delegate Access screen will look similar to this:

And that’s it!

What is the Document Root Folder?

How to Change the cPanel DocumentRoot

Step 1)  Use nano or your preferred text editor to edit the files. Once the content of each file will open in the editor, you will have to update the “documentroot” value to the new path in the following files:

/var/cpanel/userdata/cPanelUsername/domain.tld
/var/cpanel/userdata/cPanelUsername/domain.tld_SSL

In our example, we’ve modified the documentroot from /home/cPanelUsername/public_html to /home/cPanelUsername/zen/public

Tired of hassling with server management?  ChemiCloud is the managed hosting solution designed to save you time and money! Check out our web hosting plans!

Step 2) The next step is to remove the existing cache files:

rm /var/cpanel/userdata/cPanelUsername/domain.tld.cache 
rm /var/cpanel/userdata/cPanelUsername/domain.tld_SSL.cache

Step 3) Rebuild the cache files and the Apache configuration file:

/scripts/updateuserdatacache
/scripts/rebuildhttpdconf

Step 4)  Restart Apache:

/scripts/restartsrv_httpd

After following the steps described in this tutorial, the primary domain of your cPanel account will be loading the content from the new documentroot that you’ve set.

Not to worry! This tutorial will get you sorted in no time flat!

How To Fix WordPress Image Upload Issues

If you’re uploading larger files, you may encounter an error because your Maximum File Upload Size is lower than the total size of the files you’re trying to upload. You can fix this quite easily.

Increasing the Memory Limit in cPanel

Step 1: Login to your cPanel.

Once your cPanel is open, look for the Files section and open the File Manager.

Step 2: Scroll down and look for the Software section. Inside this area, click Select PHP Version.

Step 3: Once the PHP Selector opens, click the Options tab at the top.

Step 4: On the Options page, scroll down and look for two options. The first is called post_max_size, and the second is upload_max_filesize.

Generally, these should be the same, or the post_max_size slightly higher than the upload_max_filesize.

At ChemiCloud, the default for both of these is 100M (Megabytes). Since you’re likely going to upload more than 100 Megabytes of files at once, you can increase these to 1 Gigabyte.

In the latest version of cPanel, the changes are saved automatically. You don’t need to look for a Save Changes button.

Struggling with WordPress troubleshooting? ChemiCloud is the hosting solution designed to save you time and money! Try our Managed WordPress Hosting plans for just $1!

Now, return to your WordPress site, refresh the Media Library page and try to upload your files again. If you don’t get an error, you’ve solved your problem.

Increasing the Memory Limit in wp-config.php

Step 1: Locate your site’s configuration file (wp-config.php). It’s usually in your site’s root directory, where your WordPress site is installed.

Step 2: Once you have located the wp-config.php file, you must edit it.

Step 3: Add the following lines of code at the bottom of your wp-config.php file.

define( 'WP_MEMORY_LIMIT', '1024M' ); // increases WP base (front-end) limit
define( 'WP_MAX_MEMORY_LIMIT', '1024M'); // increases WP admin (back-end) limit

The above lines of code will increase your WordPress front and back-end memory limit to 1024M.

After changing the memory_limit, return to your WordPress site and check if you are getting the same error.

Now, return to your WordPress site, refresh the Media Library page and try to upload your files again. If you don’t get an error, you’ve solved your problem.

If the steps above didn’t solve your issue, you might need to restore the website files from a backup if you have one available. If you’re a ChemiCloud customer, you can rest easy!

Sleep like a baby with ChemiCloud’s nine different backup options for your sites through JetBackup. Check out our WordPress hosting plans!

Typically users who encounter this error can still access their /wp-admin pages and their main blog page, but when they open specific posts, they are greeted with a 404 error. Don’t worry, your content is still there. This error typically happens when something happens with your .htaccess file. For example, it may have been deleted or become corrupted. However, this error can also happen when something has gone wrong with Rewrite Rules.

How To Fix WordPress 404 Error

If your .htaccess file has become corrupted or was accidentally deleted, you can easily recreate it by updating your permalinks.

To do this, login to your /wp-admin, and hover over Settings on the left, then click Permalinks.

Once your Permalinks page has opened, click the blue Save Changes button at the bottom.

You aren’t actually making any changes but when you click Save Changes, a new .htaccess file will be generated with the default settings.

These default WordPress .htaccess settings appear below for reference:

# BEGIN WordPress

RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

# END WordPress

After saving your changes, return to your website and try to load an individual post.

If it loads without a 404 error, congrats, you’ve solved your problem!

If the steps above didn’t solve your issue, you might need to restore the website files from a backup if you have one available. If you’re a ChemiCloud customer, you can rest easy! All our WordPress hosting plans come with 30 day daily offsite backups allowing them to be quickly restored.

Fixing these is pretty easy if you know what you’re looking for.

How To Fix A Syntax Error in WordPress

The first step would be to find out what’s causing the error for your website. For this you will have to enable debugging mode for your WordPress website.

You can easily do this this from your site’s configuration file also know as wp-config.php file, that’s located in the directory where your website has been installed.

If you are using cPanel, you can easily edit the file using the online File Manager feature. If you are not using cPanel, then you can connect to your hosting account using an FTP client.

The next step is to edit the wp-config.php file and look for the following line of code:

define( 'WP_DEBUG', false );

In order to temporarily enable debugging mode for your website, you’ll have to set ‘WP_DEBUG’ to true instead of false. So the line of code would look like:

define( 'WP_DEBUG', true );

Now that the debugging mode has been enabled, you can return to your website and try to access it again. You will notice that instead of showing that “There has been a critical error on this website” generic error, it will reveal the actual error that’s causing troubles to our website. Like the one below, which is related to our case.
So as you can see, in our case the website complains about a syntax error on the theme’s functions.php file which is located in wp-content/themes/twentytwentyone directory.

Find the file which is giving you a Syntax Error. If you review the error message you receive, you will see the directory path and file name causing the error, as well as the line on which the error occurs.

Struggling with WordPress troubleshooting? ChemiCloud is the hosting solution designed to save you time and money! Try our Managed WordPress Hosting plans for just $1!

The next step is to connect to FTP to your hosting account. After you open the theme folder, look for the file. In our case, it’s functions.php.

If you are using File Manager in cPanel, it has an integrated HTML Editor, which you can access by right-clicking the functions.php file (or the file causing the error in your particular case) and choosing Edit.

A new tab in your browser will spawn and you will see the codebase that outlines the structure of this themes functions.php file. Don’t worry if this seems overwhelming, we’re only looking for the correspondent line indicated in your error.

If you find it challenging to figure out what’s causing the syntax error, you can try using a syntax validator online tool. Once you’ll manage to fix the syntax error you should save the changes.

Now, open a new tab in your browser and try to load your website. If it works, great! You solved your issue! Congrats!

The final step is to edit the wp-config.php file and to disable debugging mode for your website:

define( 'WP_DEBUG', false );

If the steps above didn’t solve your issue, you might need to restore the website files from a backup if you have one available.

If you’re a ChemiCloud customer, you can rest easy! All our WordPress hosting plans come with 30 day daily offsite backups allowing them to be quickly restored.

On rarer occasions, you may see a critical error message instead of the white screen of doom:

The error is still the same whether you see a white screen or a critical error message. This can happen for a few reasons, including bad themes and plugins or if there’s an issue with the webserver. Due to the variety of causes for this error, troubleshooting it can take some time.

Below, our troubleshooting tips should get you up and running quickly if you encounter this error!

#1 Is the problem happening on other WordPress Sites you have at the same host?

Suppose other WordPress sites that are hosted under the same account at your web host are also having this problem. In that case, you should reach out to our Happiness Engineers if you host with ChemiCloud, and if you don’t, you should contact your web host and ask if there are any server-related problems + let them know you’re getting the white screen of doom in WordPress.

#2 Increase Your Memory Limit

Sometimes you might be trying to do too many things at once and exhaust, or use up, all the available memory. For example, if you are trying to upload too many files to your media library at the same time, you may encounter this white screen of doom.

We have a great guide on how to increase the PHP Memory Limit in cPanel here.

#3 Deactivate All Your Plugins

If you’ve previously increased your memory limit to 512M or even 1G or 2 G, and your WordPress site still didn’t back, you need to check, you will need to do some further troubleshooting.

If you can’t get into your wp-admin because of the ‘white screen of doom’, the steps below will help you. Regrettably, WordPress doesn’t have a way to deactivate all plugins with the click of a mouse.  To do this, you’ll need to use the File Manager in your cPanel.

Step 1: Login to your cPanel. There’s a lot of ways to do this, but the sure-fire easiest way is to login to your Client Area, then open your cPanel.

Step 2: Once your cPanel is open, look for and open the File Manager under the Files section.

Step 3: Once the file manager opens, navigate to the directory where your WordPress configuration is installed. This is most likely in your public_html folder.

Step 4: In your File Manager, open the folder called wp-content:

In your wp-content folder, look for another folder called Plugins.

Right click the folder, then choose Rename.

Step 5: To deactivate all plugins at once, rename the plugins folder to something like “plugins.deactivated” just without the quotes.

Once you select Rename File, your plugins will be deactivated. Now you can return to your WordPress site and see if you can log in to your wp-admin area without issue.

Essentially, WordPress looks for the Plugins folder to run plugins that are installed, and let’s face it, you probably have plugins. When WordPress can’t find the Plugins folder, it deactivates all plugins.

Step 6: Now, you need to return to the File Manager, open your public_html folder, then the wp-content folder, just as before, except you need to rename the Plugins folder back to Plugins.

Next, rename the folder ‘plugins’, but without the quotes, and click Rename File.

Step 7: Now, return to your wp-admin and go to Plugins. Then, one by one, enable your Plugins until your site displays the Internal Server Error.

When that happens, you know which plugin is causing the issue. Repeat the process above to deactivate all plugins, then when you are able to get back into your wp-admin, delete that plugin before re-activating it.

Struggling with WordPress troubleshooting? ChemiCloud is the hosting solution designed to save you time and money! Try our Managed WordPress Hosting plans for just $1!

If that solved your problem, congrats! If not, keep reading!

#4 Use WordPress Recovery Mode

Back in WordPress 5.2, the developers introduced fatal error protection. Sometimes WordPress can catch an error and stop it in it’s tracks, especially if it’s with a plugin.

In the event you see an error that says:

You should receive an email to your admin email address with more details.

The email will say something to the effect of:

Howdy!

Since WordPress 5.2, there’s a built-in feature that detects when a plugin or theme causes a fatal error on your site. 

In this case, WordPress caught an error with one of your plugins: <Plugin Name>

The email will also contain a special link that will allow you to get into your /wp-admin so you can disable that wonky plugin and get your site back up and running.

#5 Clear Your /wp-cache

If you’re hosting with ChemiCloud, you’re running on LiteSpeed Servers and should have the LiteSpeed Cache Plugin installed in your WordPress to benefit from the speed of our servers truly.

To clear your LiteSpeed Cache, login to your /wp-admin and look for the LS logo at the top. Hover over the logo and click Purge All.

Now, please return to your website and try to open it. If it works, congrats! If not, keep trying with the next step below.

#6 Enable Debug Mode

If the steps above haven’t helped, the next step would be to enable debug mode and read through it’s output to locate the exact cause of the issue. Use the steps below to edit your wp-config file and enable debug mode.

Step 1: Login to your cPanel. There’s a lot of ways to do this, but the sure-fire easiest way is to login to your Client Area, then open your cPanel.

Once your cPanel is open, look for the Files section and open the File Manager.

Step 2: Once the file manager opens, navigate to the directory where your WordPress configuration is installed. This is most likely in your public_html folder.

Step 3: Look for the wp-config file in the listing of files. Single-click the icon to the left of the file to select it.

Next, using your mouse, right-click on the file, then choose Edit from the menu.

You will see a warning like the one below:

95% of users can proceed and click Edit.

A new tab in your browser will spawn and you will see the codebase that outlines the structure of this themes wp-config.php file. If it feels overwhelming, don’t worry, we’re only looking for the section below:

 * For developers: WordPress debugging mode.
*
* Change this to true to enable the display of notices during development.
* It is strongly recommended that plugin and theme developers use WP_DEBUG
* in their development environments.
*
* For information on other constants that can be used for debugging,
* visit the documentation.
*
* @link https://wordpress.org/support/article/debugging-in-wordpress/
*/
define( 'WP_DEBUG', false );

To enable debug mode, change the false on the last line to true. Be sure to leave the space at the end.

We can find the information we need to correctly complete this section of our wp-config.php file from our cPanel.

Step 4: Keeping the tab with the wp-config.php code open, go to the other tab where your cPanel File Manager is open, and click the CP logo in the top left to return to the main cPanel screen.

Once you’re on the main cPanel screen, look in the Database section (3rd from the top) and click MySQL Databases to open this section.

Click the Save button in the top right corner to save your changes, otherwise, you’ll need to reenter this information.

Now, open a new tab in your browser and try to load your website. If it works, great! You solved your issue! Congrats!

If this didn’t resolve your issue, we suggest you open a ticket with our Happiness Engineers so they can investigate further.

If the steps above didn’t solve your issue, you might need to restore the database and site files from a backup if you have one available.

If you’re a ChemiCloud customer, you can rest easy! All our WordPress hosting plans come with 30 day daily offsite backups allowing them to be quickly restored.

Did you know Search Engines like Yahoo!, and Bing needs to crawl your website regularly, not only to search for and index newly created content but also so they can update their systems with any changes you’ve made to your website, such as restructuring or deleted content?

If you didn’t know, now you do! You can do this utilizing a specific directive added to your robots.txt file.

Among the numerous directives you can add to a robots.txt file, you can add ones that control the rate or speed at which the search engines index your site. Typically, most website owners won’t need to configure a crawl-delay for their website, but there are some cases where it may be a good idea.

Google no longer supports the crawl-delay directive, however, Bing and Yandex do support the crawl-delay directive.

This knowledgebase article will cover how to make a robots.txt file, insert the correct directive for limiting a search engine’s crawl rate, and show how to manage this setting for search engines that don’t adhere to this setting.

How to Create a robots.txt File in cPanel

We’ll be using the cPanel File Manager to create the file. First, open your Client Area to login to your Client Portal. Then, locate the orange CP icon to the right of the service you want to administer.

Once your cPanel has opened, under the FILES area, open the File Manager.

Once the File Manager opens, you’ll want to look for your public_html folder (How to find your document root in cPanel). Then double click on the globe icon to the left of public_html to open the folder.

Once the folder is open, depending on how far you are into developing your website you are, you may or may not have any files/folders in your public_html folder. Don’t worry, if you do have files/folders here, you can still complete this tutorial and not worry about it breaking your site.

In our example, our public_html folder is empty, save for the cgi-bin folder.

We can easily create an empty robots.txt file from within the File Manager. In the top left corner of the File Manager, look for the + File option, adjacent to + Folder. Click + File and a modal will open asking you for the name of the file + where you want it created:

In the New File Name box, name the file robots.txt, then click Create New File. You will be returned to the File Manager view in the public_html folder, and you’ll see the file has been created.

How To Configure A Crawl-Delay In Your Robots.txt File

cPanel’s File Manager is useful because it allows us to create the file, but we can edit it without leaving the File Manager.

To begin editing the file, single-click on the robots.txt file so that it is highlighted in semi-opaque cyan color, as shown below:

Once you have selected the file, look at the top menu of the File Manager. Several options are at the top, including + File, + Folder, Copy, Move, Upload, and others. The one we need to use is Edit. After you click Edit, a modal will appear with some information.

For the use of the robots.txt file, you can ignore this and proceed to click Edit.

A new tab will appear in your browser and you’ll be taken to something that resembles an old-school word processor. For those who don’t remember those, it’s what people used to type their letters on before the Internet.

To insert a crawl-delay, copy the text below and paste it into the editor:

User-agent: *
Crawl-delay: 1

This will ask search engine spiders crawling your website to wait 1 second between each page they crawl. If you want them to wait longer, you can use these other two settings:

User-agent: *
Crawl-delay: 5

or

User-agent: *
Crawl-delay: 10

These will ask the search engines to wait 5 or 10 seconds between page crawls.

Did you know that website speed affects SEO & Google Rankings? We use LiteSpeed caching to deliver content to your visitors almost instantly.  Check out our web hosting plans!

Your editor should look similar to the image below after pasting one of the options above:

After entering the data, click the blue Save Changes button in the top right corner. Then click the Close button adjacent to the Save Changes button.

You will be taken back to the cPanel File Manager where the robots.txt file has been created and updated with this directive.

CORS introduces a standard mechanism that can be used by all browsers for implementing cross-domain requests.

To enable it, set CORS header to the .htaccess file, by adding the following line of code:

<IfModule mod_headers.c> 
Header set Access-Control-Allow-Origin *
</IfModule>

Are you tired of slow web hosting? We use LiteSpeed caching to deliver content to your visitors almost instantly.  Check out our web hosting plans!

Fortunately, with just some simple steps, you can set up URL masking to have your visitors see what you want them to see without having to show them the full URL where the files are actually located. You would merely need to follow these steps.

For this example, we will have yourdomain.com show the contents of yourdomain.net/sitefiles however, you can replace these domain names and URLs with your specific domain names and URLs.

1) You would first need to make sure that your site is loading perfectly at domain.net/sitefiles. If it is loading correctly, you should have no problems.

2) Create an index.html file in the public_html (or www) folder on your yourdomain.com site. Also, be sure that there is not an “index.php” file in the same directory as that will take precedence over the index.html file you have created and load up when visitors access your site.

3) Add the following text to the index.html file and modify the title and frame src

<html>
<head>
<title>Your Website Title</title>
</head>
<frameset rows="100%,*" border="0">
<frame src="http://yourdomain.net/sitefiles/" frameborder="0" />
<frame frameborder="0" noresize />
</frameset>
</html>

What this will do is create a frame on the domain.com site that will fill the entire page. Then, when your visitors access yourdomain.com, they will only see the content of yourdomain.net/sitefiles.

And that’s it! You have now created a frame to mask your site’s URL.