Below is a personal list of web spiders and web crawlers that I block from crawling various sites.
This helps mitigate issues related to server load, security, and content scraping.
Carefully consider the impact on your website’s visibility and search engine ranking before applying any of my crawler blocks within this article.
Organizing your website’s URL structure is crucial for both user experience and SEO. A common challenge for WordPress users, especially those using robust themes like Avada, is separating different content types.
By default, setting a global permalink structure like /blog/%postname%/ often forces all content—including FAQs and Portfolio items—into that same directory.
This guide walks you through the exact steps to configure your WordPress website so that your blog posts, FAQs, and portfolio items each have their own distinct, clean URL structures.
Moving your WordPress blog posts to a subdirectory like /blog/ is a strategic move to separate your dynamic content from static pages, improving site structure and user experience.
This article will explain to you how to achieve putting all your blog articles under a different directory.
This article serves as a reminder-to-self regarding a recent display issue I had on one of my WordPress sites with the Avada child theme.
Within the Avada theme for WordPress you can set the padding to be a negative number so that two columns or containers overlap. This generates a nice effect.
However, after updating Avada to 7.15.3 I discovered a new option under the Performance menu (see screenshot) called: Optimize Offscreen Rendering
Turning the Optimize Offscreen Rendering on prevented the overlay from appearing despite my having adjusted the Z Index options.
No doubt they’ll have it fixed in an upcoming release, for now I’ll just leave it turned off.
If your WordPress site suddenly starts dragging, your database balloons in size, or your host sends you a warning about excessive queries, there’s a good chance the culprit is hiding in plain sight: Action Scheduler.
This background task runner powers WooCommerce, subscription plugins, backups, and countless other tools. When it behaves, it’s invisible. When it breaks, it can hammer your database every few seconds and generate gigabytes of log entries before you even know what happened.
That’s exactly what happened to one of my sites — and here’s how I fixed it.
In some cases you may want a slightly more personal login page. Here is a snippet you can use to change the default WordPress login logo, link, and title.
There was a minor update ( I am talking 2.10.0 to 2.10.1 ) for Gravity Forms which included a ‘security enhancement‘ which I implemented.
Upon doing so my WordPress based membership site, which was using the Gravity Forms User Registration Add-On completely crashed with a Fatal Error and Your Site is Experiencing a Technical Issue notice.
No big deal I thought, I would just restore the backup from the day prior. Same result, so I continued restoring older daily backups without success. Now what!?
This article covers how I was able to resolve that Fatal Error but is intended for my personal use only in order to help me jog my memory should this issue occur in the future. So I won’t be going into great detail.
By default, WordPress saves every change you make to a post or page as a revision.
While this is great for version control, it can quickly bloat your database—especially on long-form content or frequently edited pages.
In fact too many revisions can slow down your admin dashboard, cause memory issues with certain page builders (like Avada or Elementor) as well as lead to database bloat over time.
This article is a quick reference for how I automatically limited the number of stored WordPress revisions.
Just had a single page scroller website designed for a client. I applied my final revisions only to have the backend editor within Avada disappear. Within the Revisions screen element it displayed a Critical Error has occurred on this site.
Pardon the brevity of this article. I’m simply publishing this on my site so that I can recall how I fixed this issue should it occur again on another site.
Sometimes your connection with a site will fail as well as any attempts to reconnect it the ManageWP service.
This article covers a potential solution to the issue of sites failing to reconnect once the connection drops.
