25

Google will automatically remove pages that now return a 404 status. They will get removed 24 hours after Googlebot next tries to crawl them. If you want to speed up the process slightly, return "410 Gone" status for those URLs instead. Then they will be removed without the day grace period after they are next crawled. The only problem is that it ...


5

This certainly looks like a mistyped URL in the links on pages /blog/page/12/, /blog/page/13/ and /blog/page/14/. On those pages look for a link like the following: <a href='’https://go.example.com/20190620-Lyft-Livestream.html?ref=blog'>Link</a> The erroneous single back curly quote ’ at the start of the URL will trigger the user-agent (...


4

You do not say what the .sql file is for, however, a .sql file, in of itself, is just plain ol' text and therefore not a threat. Ignore it the notice. It is not uncommon that anti-virus software will hit on various files. They are looking for patterns. Known JavaScript files are often pinged as a virus. That said, if you do not know what the file is or if ...


2

It is possible and WordPress is set up by default to allow static files. WordPress uses a front controller to have index.php handle all the URLs. But it has an exception for any static file that actually exists. The code WordPress uses in .htaccess to do this is: RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /...


2

Well... I fixed it! But as it usually goes, I'm unsure of the exact thing that put it together. However, I will leave what I did over here, in hopes that it might help someone else in the future. From cPanel, I first changed my php version from 7.2 to 7.1. And it crashed my website. Therefore, I changed it back to 7.2, and voila! It simply works.


2

You can verify that Yoast does indeed 301 (permanently) redirect attachment pages by viewing the Media Library and copying one of the attachment page URLs into a HTTP header check tool. (Yes, they do.) Once everything is 301 redirected, it will eventually be updated in Google's index. This can take some time, so you could use Webmaster Tools to ask Google ...


2

Thanks to the comment by @closetnoc and the helpful link to nvd.nist.gov/vuln/search I was able to troubleshoot the problem. The solution is a fresh reinstall of Wordpress on the server (Bluehost helped me with this) and then a backup from VaultPress (If you have VaultPress). Otherwise, manually add the backups, but don't add the core files. Since those were ...


2

It is not uncommon for malicious JS to be injected and stored in a database. If this is a backup copy of your site's database, it may contain elements that have been identified as malicious. It looks like this is the case based on what you've found in the SQL file. I would find another reputable scanner that runs on the server and see what it finds, then ...


2

This problem won't be solved by pinging Google to recrawl your site or resubmitting the sitemap because it would index the new URLs and not delete the old/dummy ones. The Webmaster tool used for URL removal is the only way to ask Google to remove links from its index, however, it only allows one link at a time, to be submitted for removal. In order to ...


1

If you don't have to ask users to send some personal info and don't have online payment function, then you don't need Full (strict) certificate. Full SSL As it should be evident by now, Full SSL will mean a completely secure connection. You will have a fully secure connection between your visitor and CloudFlare and also a secure connection between your web ...


1

Essentially, your biggest problem is that you have 78 broken links. You need to find and fix those--mostly because people will get stranded looking for your content. Switching to a different platform or reinstalling your site to the existing platform is likely to make this kind of issue worse before it gets better. Find a good analytical spider (I use this ...


1

All of your errors look fixable to me. It is a lot of work to switch to a different website framework or content management system. Fixing broken links is relatively easy. None of those errors or warnings are going to prevent Google from indexing or ranking your content. Fixing the issues may improve SEO slightly, but none of the issues are going to ...


1

I helped transfer a site out of Wix. Wix allows you to use them as a domain registrar and DNS host without a Wix site. They are able to point your domain to external hosting. Rather than editing Settings > General you should be editing your DNS settings. To edit DNS records: Go to the My Domains page. Note: If you have more than one ...


1

In the past, there have been several bugs related to AMP pages showing up in desktop searchers, that might be another one. In addition to that, Google has been suffering in the last 5 months several bugs related to the indexation of new content. This is being a hard year for Google as they are changing a lot of things. My guess is that is just a bug that ...


1

There is no relation between the Wordpress administration language and the site language. You can set language options that affect SEO through these two ways: International targeting (Google Search Console) Hreflang tag Nothing else would impact the SEO strategy. Many people still believe that HTML lang is used by searchers but, at least Google, ignore it:...


1

# BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / # Additional rewrite rules go here RewriteRule ^[0-9]{4}/[0-9]{2}/(.*)$ /$1 [R=301,L] : Any custom mod_rewrite directives, such as your "redirect" should go before the # BEGIN WordPress section. You should avoid editing between the WordPress comment markers as WP itself tries ...


1

OK. So after having spelled out the question and posted it, I finally found the solution in this blog post. # BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / # Additional rewrite rules go here **RewriteRule ^[0-9]{4}/[0-9]{2}/(.*)$ /$1 [R=301,L]** RewriteRule ^index\.php$ - [L] RewriteCond %{...


1

Since this is a WordPress site, you presumably have other mod_rewrite directives in your .htaccess file to drive the WP "pretty" permalinks. The behaviour you are experiencing would seem to be consistent with having put the redirect directives in the wrong place, ie. after the WordPress front-controller*1. This redirect must go before the existing WordPress ...


1

I got exactly same problem when deploy HA Wordpress on EC2 Apache web server under auto scaling group when spin up new EC2 Apache web server. 1. At first I think there are problem with apache web server: sudo vim /var/log/httpd/error_log [Tue Nov 05 ] [core:notice] [pid 2914] AH00094: Command line: '/usr/sbin/httpd' [Tue Nov 05 ] [mpm_prefork:notice] [pid ...


1

The HTTPS version displays the security warning of course (as there is no SSL certificate) and then a 404 if you go past that. If you get a "security warning" that you are able to bypass then the server is listening on port 443 and there is a security certificate installed but for a different domain/hostname. When you bypass this invalid certificate then ...


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