Find out what Plugins a site is using

Discover which plugins a website uses.

The WPTD analyzes the link for you and shows which themes and plugins the website uses. This is the result of one of my pages after using the command "WPScan":. There is no need to enter the code of the website to find out the CMS of a website. When you see a Wordpress plugin that you want to use in a blog, there is a good chance that you can use a scanner tool to identify the name of the plugin that you are using.

To find out which plugins a WordPress blog uses

These are many good reason why you might want to do a little investigative work to find out what a website uses to operate itself. Perhaps they have a very appealing features that you would like to use for your own website. Perhaps you are conducting a survey and want to find out which plugins are most often used on large web sites or simply in your competitor or marketplace.

Perhaps you would like to make an impression or make a spoof and imitate the originals as accurately as possible. Whatever your goal may be, you have several ways to discover plugins. I' ll also give you some hints on which plugins you want to use, no matter what your research shows you.

I' ll say this in advance; you probably won't be able to get a complete listing of plugins for a particular site unless you have a public listed plugins listing or directory. Another annotation, many of them will also help you identifying the topic that a WordPress blog uses.

If the design is fully customized, it won't help you much, and it may not help if the blogs take a design and edit it, but it will bring you nearer to the right place. It is a very fast reference utility that, I think, basically searches only the sources of a website that searches in the usual places for all the information it can find.

Its main purpose is to find a topic at which point it will look up that topic and see what versions the website is up, where the topic can be found, and even insert the topic descriptions from whatever website. Once the topic is recognized, the website will do the same with plugins.

There will be a plug-in, its name and a thumbnail, a flags if it is liked, the provided descriptions and a links to the downloads. There will also be whether the plug-in is free or not. This WordPress has recognized WordPress by Yoast and W3 Total Cache, WP Shortcode, WP Review and Speed Booster Pack for a test page I use for each of these utilities.

It recognizes W3 Total Cache, Google Analyticator, Yet Another Related Posts plug-in, WP Socialite, DT Author Box, WP-PageNavi and Ultimate Social Deux for this Blog you are currently viewing. Scanning a website will take a while to detect every possible plug-in, and this is because it has a large data base that can be compared with the source of a particular website.

Specifically, this utility is provided by a corporation that has developed and released 15 WordPress plugins, among them CMS Tree Page View, Easy History, Nice Navigation and Hundstall 404. Well, if you've never even read about it, that's fine; you're a Sweden -based corporation, and your plugins aren't really widely distributed worldwide.

A disadvantage of this check is that it only verifies the existence of 65 plugins. Fifteen of these plugins are the 15 published by the corporation itself. Other 50 contain the 50 most common plugins that WordPress itself lists. The complete checklist can be seen below the check.

On my test site, however, it found nothing. It is interesting because we know that the site uses W3 Total Cache, WordPress Yoast and some other WordPress features on the site cache. Now I' m quite sure I'm not using every one of them, so I'm going to get up here and say there's a little imprecision with the page checks.

Still, it can find some plugins for you. Posted on What WP Topic is That Dot com, this site is a quicker and more liquid locator. If you run it, the topic detail is listed, along with name, home page, creator, title, description, release, licence, and screenshots. Plugins will then be searched for. On my test page it will list OfficePress SOE after Yoast, WP Shortcode, WP Review, Speed Booster Pack and W3 Total Cache.

How about this page? It is a much more rugged way of searching, but it is not intended to look up WordPress plugins or topics. There will be some such information when it finds it, but it goes further, further beyond, to provide more details about the particular architectural design. Like, let's see what it says about my test page:

As you can see, it accurately detects three of the five WP plug-ins that identify the other exams. The program also detects Jetpack, which is usually preset for WordPress installation, so that it is displayed for almost all of them. It is more geared towards dragging page architectural detail than digging into the WordPress source text.

It will not detect as such any plugins that are not uniquely detected in the source tree. More than that, if the website visitor uses a customized encoding framework, it is not detected. It is a little ploy you can do to see what the site administrator has posted.

Recall the beginning when I said if you had accessed the plugin directory you could have learned a great deal? Sometimes the administrator forgets to create this directory so that you can find it in Google searching. Well, I'm saying this right here, it won't work most of the while.

There is something on most websites, either a plug-in, a site manager or a little something that makes a lot of sense hiding this directory from Google. It' not good to keep it open, because a hacker can detect plugins and use those plugins as attacking tools when they detect errors. When you find a website that has disclosed it, I really suggest that you send them a note to inform them of the possible misuse as soon as you have received the requested information.

Make sure you don't unintentionally blogs your entire website, that would be terrible. It is another way to find out what is present in the files, although it is a little more handbook and may require a little bit of interpreting. First thing you want to do is to display the crude sources of the website you are trying to examine.

It is the filename that plugins will use with WordPress, and usually you will see an item containing this filename followed by the name of the plug-in. It' usually a references that is part of a scripts that gets this plug-in in use. It can also show you some interesting things about the page and how the plugins are loaded, e.g. where and in which order they are loaded.

It can even help you in diagnosing loading speeds when a suspended plug-in is blocking website loading time. It can also help you to detect some custom-made plugins, or at least recognize when there are plugins in use that were not found in the other queries.

Naturally, you have to be able to interprete what you see. It is a kind of last way out but it is also a possible first step if you think that the website owners are open for you. For example, you cannot get any of the operators of these pages to reply to you about topics or plugins.

The only thing you really need to do is write them a friendly note and ask them what plugins you are using. I' m saying right now, if you're looking to create an impersonation site, they probably won't be that useful. A webmaster is prone to paranoia about copies of contents, and that includes brands and topics as well as current blogs.

Well, if they use a shared free design, that's another thing, but still, take care. WordPress.org has ten thousand of WordPress plugins available, and if you look at third-party developers on their own pages and using aggregate tools like CodeCanyon, there are really no limits to what you can do with plugins.

However, if you use plugins, you will want to obey some simple guidelines and probably want to use some custom plugins to make sure that you can keep up with the feature. Always, always, always, make sure your plugins are up to date. From time to time I might suggest using a plug-in that hasn't been upgraded in a few years, but these are universal and uninstallable help plugins, not general website functions.

There are two reasons why you want to keep your plugins up to date. With age, a plug-in is more likely to have an interacting experience with someone that can give them vicious traffic to your site. Lots of favorite plugins will over the course of your lifetime be adding functions that will give your plugins a more rugged part in your blogs day.

Conditionally, if a plug-in is one of these one-shot utility programs, make sure you deinstall it and delete any remaining file. When a plug-in has not been upgraded in a year, it's a good idea to find a new one that will replicate the feature set, or to do without it. You should also always make sure that you use too many plugins at once.

Location loading time. More plugins you have, the longer it takes to download your website. Plug-in encoding. So, the poorer the plugin encoding or the more efficient it is, the less responsive your website will be. Plug-in conflict. If you have more plugins, the more possibilities there are for a particular functionality or features to abort due to the action of another one.

There is no way to use a plug-in that changes the way plug works, and then another plug that is based on standard plug, for example. It is also a good idea to be wary when trying to test and deploy a plug-in. When you don't like it or when it is not backed up, you can encounter the problem where you want to delete it and find another one, and try again.

But the problem is that plugins on WordPress are not in the sandbox. These footprints can collide with or injure other plugins, and make your site untidy. It may even be necessary to completely reinstall WordPress after a while. It is best to work selectively with the plugins you are installing.

There is a long list o plugins that can be used on a new website. The full story can be found here, but I will be listing the plugins below if you want to look them up yourself and jump over our argument. You can adjust your plug-in workload from there. Maybe you want more picture focussed plugins, or you don't necessarily need the smartslug or the defective linkedcheckers.

It' s up to you what you think is best, of course.

Mehr zum Thema