Although WordPress is currently the most popular and powerful CMS, you should be very careful when editing and changing it. A few mistakes can ruin the entire site and ultimately make it inaccessible to users that degrade the reputation of the website.
It is the most popular and widely used, so you can find solutions to all the problems you face on the Internet, such as WordPress blogs and forums.There are common errors that WordPress website owners face more often. Some of these common mistakes are WordPress posts that return database connection errors, internal server errors, and 404 errors.
If the requested URL is not found on the web server, a 404 error occurs. This article describes how to fix a WordPress post that returns a 404 error.
The only good thing about posts that return a 404 error is that they can access the main blog. If a particular post is inaccessible, the user will get a 404 error.
If a user directly visits the article in the search engine results, it will definitely be the worst experience for him, and will ensure that the search engine does not list the posts and that the overall SEO of the website will be affected.
The main reason for a 404 error is that you accidentally deleted the .htaccess file or there was a problem with the rewrite rule. There are various ways to fix a WordPress post that returns a 404 error depending on the cause of the error.
Correcting WordPress posts that return a 404 error –
Wrong comment that most people will only redirect if a 404 error occurs. Redirecting is a temporary solution, but you need to find out the root cause of the error. Too many 404 errors on your website will lower your search engine ranking due to poor user experience.
Step 1. One of the basic solutions that returns a 404 error is to modify the permalink. Just go to the Dashboard and select Permanent link in Settings on the left menu. Click the Save Changes button without making any changes. Update the permalink settings and refresh the rewrite rules that may be causing the problem.
If step 2 does not resolve the problem, you will find the .tac.h file. Therefore, you must connect to the web server via FTP and look for the .htaccess file in the root folder.
You must specify the permissions as 666 to make the file writable. If you add the following code to your .htaccess file and then change the file permissions to 660, your website could be hacked.
# BEGIN WordPress
Turn on the rewrite engine
RewriteBase /
RewriteRule ^ index .php $ - [L]
RewriteCond% {REQUEST_FILENAME}! -f
RewriteCond% {REQUEST_FILENAME}! -d
RewriteRule. /index.php [L]
# END WordPress
Step 3. If the problem is not resolved, you should look elsewhere. It is common for web developers to develop new sites on the local server before sending them to the web server. However, the permalinks often used for local servers are awkward, and you can change the rewrite_module in the Apache configuration of a tool that uses tools such as WAMO or MAMP to change the permission link of the web server and make it look like a web server. This process is referred to as enabling custom permalinks on WordPress local servers.
How to use a custom persistent login on a WordPress local server
One easy way to fix a WordPress post is to grab a 404 error. To do this, click the WAMP icon in the icon tray on the taskbar and navigate to the Apache and Apache modules. Enable rewrie_module from the drop-down list. Then the custom permlink structure works perfectly, and you’ll see a message that the page can not be found.