New answers tagged

1

It could be the infamous WordPress "White Screen of Death" which occurs when WordPress experiences a fatal error with debugging features disabled, such as to not dump potentially sensitive information to end-users. Refrain from enabling WP_DEBUG in live environments in the course of troubleshooting the issue as it may expose an installation to additional ...


5

Security issue? Doubt it. It just makes your site more visible to people who likes to attack wordpress sites. Other than the visibility everything is the same, security through obscurity is not something you should rely on anyway. Useless? Definitely. There is no reason to allow indexing of your admin login in your site. You don't want your users finding a ...


7

When a new bug is found, in this case in wordpress, the first thing hackers will do is try to find vulnerable sites that use wordpress. A good way of doing it is trying to find wp-admin pages on google. Maybe will even use automated tools to find-and-exploit sites based on that. Avoiding that would be the main security reason for doing it. If you have no ...


5

Google doesn't want to index non-content pages including admin pages and pages that ask you to login. Putting wp-admin in robots.txt is better for SEO because it will usually prevent the page from being indexed. It is possible that an attacker will do a Google for all sites that have wp-admin in the URL. Keeping that page on your site out of the Google ...


1

wp-admin on wordpress is direct entry to your admin panel. That's why google wants you to disallow it. And... in this case, listen to google and srsly, disallow it. It's good practice :)


4

cPanel can do this by going to the following url: http://[ip-address]/~[cPanel-username]


0

This is what I learned (and yes I fallen in the same trap before), and I'm assuming you'll use a common template for your sites. If you use a subdomain, it will be treated as a separate website. If you're making a blog via a subdomain, then at least have other pages attached to that subdomain as well and accessible so that your blog does not look like a ...


1

You would be far better off with a sub-domain hosted somewhere else, such as... say... Wordpress.com! This would (hopefully) ensure that your WP install is always fresh and all updates have been applied and that your WP site stays as safe as possible. This would not require a redirect. Just a link. There are quite a few hosts specifically designed for WP ...


1

The important thing is to place your external redirects before the WordPress internal rewrites (as Mike suggests in his answer). The WordPress rewrites are a "catch all" and rewrite everything. So if you place any rewrites/redirects after the WordPress stuff they will simply be ignored. RewriteCond %{HTTP_HOST} ^www\.example\.com$ RewriteRule ^/?$ ...


3

# Use PHP5.4 as default # Changed PHP handler from application/x-httpd-php54 to application/x-httpd-phpbeta on Thu Dec 17 16:50:26 MST 2015. AddHandler application/x-httpd-phpbeta .php # BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / # Insert redirect based rewrites here. # Example: RewriteRule ^redirectme$ ...


2

I guess you're using WordPress based on the get_post_permalink() so try replacing <?php echo get_post_permalink(); ?> with <?php echo get_post_permalink().'?utm_source=whatsapp'; ?> to append the attribute onto the link.


1

Your site is hacked. Somebody likely installed software on your site that is doing the redirects. It is probably also showing some content only to Googlebot. You need to clean up your hacked website. Google has an entire webmaster help section dedicated to hacked sites: https://www.google.com/webmasters/hacked/


0

It is always considered a good seo practice to non index categories and tags. Google considers these pages as duplicate as the same title & post excerpt is used across all those indexed pages. In order to get rid of Google’s penalty, you’ll need to no-index categories and tags on your blog. If you are using wordpress you can use seo by yoast plugin and ...


2

Try this if you have rewrite module installed: RewriteEngine On RewriteCond %{REQUEST_URI} ^(.*)wp-login.php$ RewriteCond %{REMOTE_ADDR} !^xxx\.xxx\.xxx\.xxx$ RewriteRule ^(.*)$ - [R=403,L] replace the xxx's with each octet of your IP address. For example, if your IP address is 111.222.333.444, then replace RewriteCond %{REMOTE_ADDR} ...



Top 50 recent answers are included