Group items tagged

ohnmu4 points · 5 days agoDoesn't matter. You can also just use a comment like:# there are not robots.txt directives here

Using this implementation, it’s important not to noindex or block paginated URLs using robots.txt

If you’ve already implemented rel=prev and rel=next tags, there is no need to remove them. Bing and other search engines still use the tags, and they are used for web accessibility plus W3C compliance.

Pagination method 1: continue using multi-page pagination with self-referencing canonical tags to each page in the series. Keep rel=prev and rel=next if you’re already using it.

Block ads to prevent sophisticated attacks that masquerade as images. Use VPN for end-to-end encryption whenever you’re working at public WiFi hotspots to prevent session hijacking and MITM attacks.

if you are going to keep them on your pages, make sure they are implemented correctly. You do have to take the time to learn how to follow the specs carefully and get it right. Putting aside the prev/next tags for a moment, let’s think about how you should implement pagination otherwise on your page. Our first preference is to implement that pagination in clean HTML tags that are visible in the source code for the pages on your site

The second choice would be to implement it in a way that isn’t clinging to the source code, but you can actually see it in the DOM or the Document Object Model. That means that your links are going to be anchor tags with a valid href attribute, not span or button elements with attached JavaScript click events.

consider including just your site name at the beginning or end of each page title, separated from the rest of the title with a delimiter such as a hyphen, colon, or pipe

Differentiate the descriptions for different pages. Identical or similar descriptions on every page of a site aren't helpful when individual pages appear in the web results. In these cases we're less likely to display the boilerplate text. Wherever possible, create descriptions that accurately describe the specific page. Use site-level descriptions on the main home page or other aggregation pages, and use page-level descriptions everywhere else. If you don't have time to create a description for every single page, try to prioritize your content: At the very least, create a description for the critical URLs like your home page and popular pages.

Programmatically generate descriptions. For some sites, like news media sources, generating an accurate and unique description for each page is easy: since each article is hand-written, it takes minimal effort to also add a one-sentence description. For larger database-driven sites, like product aggregators, hand-written descriptions can be impossible. In the latter case, however, programmatic generation of the descriptions can be appropriate and are encouraged. Good descriptions are human-readable and diverse. Page-specific data is a good candidate for programmatic generation. Keep in mind that meta descriptions comprised of long strings of keywords don't give users a clear idea of the page's content, and are less likely to be displayed in place of a regular snippet.

A very worrisome fact about website hacking statistics and hacking websites is that 98% of WordPress vulnerabilities are related to plugins. (See Figure 7 below.) The most popular vulnerability types in WordPress plugins are Cross-site Scripting and SQL Injection. According to CVE Details, XSS attacks are the biggest threat to WordPress sites. The second most popular type of attack is code execution and third are different bypass vulnerabilities. What is even the most worrisome is that in these top 10 WordPress plugins listed you can see 5 commercial plugins, they have around 21 million downloads and one of these plugins is a security plugin. (Source: WP WhiteSecurity) Source: WP WhiteSecurity To top it off, even more, the sad part is that anyone can create a plugin and publish it — WordPress is open source and nobody is performing a code analysis before the new plugin is sent out for the world. Also, there are no serious security standards for these plugins hence, WordPress plugins are unfortunately prone to vulnerabilities.

The WordPress extension WooCommerce lags far behind in last place. Just under half of the WooCommerce shops currently meet the Google specifications. An alarming 26% are actually bad. The self-operated hosting solution with low-performance mass providers is clear here.

Concierge Restore

ChangeAlert Notifications

MalwareGone™ Remediation

Less flexibility with regard to plugins and software versionsLimited access to account configuration options

With shared hosting as mentioned above, you are usually given account level access to the server so that you can manage your website. Root level access is only available to your hosting provider, which means that they take care of all of the server management responsibilities. If you need a higher level of server side customizations, then a VPS or Dedicated server may be for you. 

Managed VPS and Dedicated servers include several beneficial options:Fully managed Server (Linux, cPanel, etc)Technical support for server problemsAssistance with server side customizations such as PHP modules, firewall rules, etc.