You can check if a website is built with WordPress by inspecting the page source code, testing the login URL, or using an automated detector. Most sites reveal their platform through specific file paths, generator tags, or standard login directories. This guide walks you through the exact steps to verify the backend, even if the site owner has tried to hide it. You will learn how to spot WordPress signatures in the HTML and how to use free tools to confirm your findings in seconds.
Why do you need to know if a site uses WordPress
Knowing the underlying technology helps you understand how the site was built. If you are a developer, this tells you which plugins or themes might be in use. If you are a business owner, it helps you evaluate competitors or plan your own site migration. WordPress powers a large portion of the web, so it is the most common platform to identify. However, not every site uses it. Some use custom code, Shopify, Wix, or other CMS platforms. Identifying the correct platform prevents you from wasting time on the wrong technical approach.
Check the page source code for WordPress markers
The most reliable manual method is to view the source code of the page. You do not need to be a programmer to do this. On your computer, right-click anywhere on the website and select "View Page Source" from the menu. A new tab will open with the HTML code. Press Control and F on your keyboard at the same time to open the search bar. Type "wp-content" into the search field. If the site is built with WordPress, you will see multiple instances of this string. These paths point to the folders where WordPress stores themes, plugins, and images.
Look for links that end in .css or .js files. If you see paths like /wp-includes/js/ or /wp-content/themes/, the site is definitely WordPress. You can also search for "wp-includes". This directory contains core WordPress files. If your search returns zero results, the site might not be WordPress, or the owner has heavily customized the file structure.
If you want a faster way to run this check without opening the source code manually, you can use a free website technology checker. It scans the page and tells you if WordPress is detected based on the same file paths and headers, saving you the manual search step.
Test the standard WordPress login URLs
WordPress sites have a default login page at a specific address. You can test this by typing the website domain followed by /wp-admin/ into your browser address bar. For example, if the site is example.com, you would type example.com/wp-admin/. If the site is WordPress and has not changed its login URL, you will see the standard WordPress login screen. It usually has a blue header and a white form asking for a username and password.
If you see a 404 error page, the site might not be WordPress. Or, the owner may have moved the login page to a custom URL for security reasons. Many security plugins allow site owners to change the /wp-admin/ path to something obscure. Do not assume the site is not WordPress just because this test fails. It is a strong indicator, but not proof. You should combine this test with the source code check for certainty.
Look for the generator meta tag
WordPress automatically adds a meta tag to the head section of every page. This tag tells browsers and crawlers what software generated the page. To find it, view the page source again. Scroll to the very top of the code, where the
section is. Search for the word "generator". If you see a line that says , you have your answer. The number after WordPress is the version.Site owners can remove this tag using plugins or custom code. If you do not see it, it does not mean the site is not WordPress. It just means the owner hid that specific marker. However, if you see the tag, it is a definitive proof. Some sites use caching plugins that serve static HTML files. In those cases, the generator tag might be missing even on a WordPress site. This is why you should always check multiple markers.
Use browser extensions for instant detection
Browser extensions can scan a website and display the technology stack in a small icon or popup. Wappalyzer is a popular choice for this. You install it in Chrome, Firefox, or Edge. Once installed, you browse to the website you want to check. The extension icon in your toolbar will light up. Click it to see a list of detected technologies. If WordPress is in the list, you know the site uses it.
These extensions work by analyzing the page source and HTTP headers in real time. They are fast and convenient for checking many sites. However, they can sometimes miss hidden installations. If the extension says "No technology detected" or lists only generic JavaScript libraries, you should fall back to the manual source code checks. Extensions are great for a quick first pass, but manual verification is more thorough.
Check for WordPress REST API endpoints
Modern WordPress sites expose a REST API. This allows developers to interact with the site data programmatically. You can test for this by typing the domain followed by /wp-json/ into your browser. If the site is a standard WordPress installation, you will see a JSON object in the browser window. This object lists available routes and namespaces. If you see a 404 error, the API might be disabled, or the site is not WordPress.
Some security plugins disable the public REST API to prevent data leakage. In that case, you might not see the JSON output. But if you do see it, it is a strong signal that WordPress is running in the background. You can also try /wp-json/wp/v2/posts. This endpoint lists the public posts on the site. If it returns a list of articles, the site is almost certainly WordPress.
Why automated tools sometimes fail
Automated tools scan for known fingerprints. They look for specific file names, cookie names, and header values. If a site owner uses aggressive caching, the tool might see a static HTML file that lacks WordPress markers. If the owner uses a headless setup, where the frontend is built with React or Vue and the backend is WordPress, the tool might only see the frontend framework. In these cases, the tool might report the site as "Unknown" or list the frontend framework instead of WordPress.
This is why manual checks are still valuable. You are looking for the underlying infrastructure, not just the surface layer. If an automated tool gives you a negative result, do not stop there. Run the manual checks described above. Look for the /wp-json/ endpoint. Search the source for wp-includes. Try the /wp-admin/ URL. These steps will reveal the truth even when automated scanners are confused.
What to do if you cannot identify the platform
If you have checked the source code, the login URL, the generator tag, and the REST API, and you still cannot confirm the platform, the site might be using a custom build. It could be a fully custom HTML and JavaScript site. It could be a headless WordPress setup with a custom frontend. Or it could be another CMS like Drupal or Joomla.
If you are trying to replicate a site's functionality, it is better to focus on the user experience rather than the technology. You can build the same features on WordPress, Shopify, or a custom stack. If you are unsure which platform to choose for your own project, consider your needs. WordPress is flexible and has a huge plugin ecosystem. It is a good choice for content-heavy sites, blogs, and small business websites. If you need complex e-commerce features, you might look at other options.
If you are struggling to decide on the right technical foundation for your business, you can explore how we approach local business websites. We build sites that are easy to manage and fast to load, regardless of the platform you choose.
Summary of detection methods
Here is a quick reference list of the methods you can use. You do not need to use all of them, but using two or three gives you high confidence.
- View Page Source: Search for
wp-contentorwp-includesin the HTML code. - Test Login URL: Visit
domain.com/wp-admin/to see if the standard login page appears. - Check Generator Tag: Look for
<meta name="generator" content="WordPress">in the head section. - Use a Browser Extension: Install Wappalyzer or a similar tool to scan the site automatically.
- Test REST API: Visit
domain.com/wp-json/to see if the WordPress API is exposed.
Each method has its strengths. The source code check is the most reliable for standard installations. The login URL test is quick but can be blocked by security plugins. The REST API test is useful for modern sites. Combine these methods to get the full picture.
Common mistakes to avoid
Do not rely on a single method. A site can hide the generator tag but still have wp-content paths. A site can block the /wp-admin/ URL but still expose the REST API. Always cross-reference your findings.
Do not assume that a lack of WordPress markers means the site is not WordPress. Some sites use plugins to remove all traces of WordPress from the frontend. This is a security best practice, but it makes detection harder. You need to look deeper.
Do not ignore HTTP headers. If you have access to browser developer tools, you can check the response headers. Look for headers like X-Powered-By: PHP/8.1 or Server: Apache. While these do not prove WordPress, they give you clues about the server environment. WordPress typically runs on PHP and Apache or Nginx.
Final thoughts
Identifying the platform of a website is a useful skill. It helps you understand how the site works and what technology it uses. By following the steps in this guide, you can confidently determine if a site is built with WordPress. Start with the source code check. It is the most direct way to find the truth. If that fails, try the login URL and the REST API. Use automated tools for a quick scan, but verify the results manually.
With these techniques, you can look at any website and know what is running under the hood. This knowledge is valuable for developers, marketers, and business owners alike. It helps you make informed decisions about your own web presence.
If you want to learn more about how different platforms affect your search visibility, check out our guide on why websites disappear from search results. Understanding the technology is only half the battle. Ensuring your site is visible and accessible is the other half.
You can also read about how to fix tracking issues on your site to ensure your analytics are working correctly once you know your platform. Proper tracking helps you understand your audience and improve your content.
For more insights on building a robust online presence, visit our contact page to ask specific questions about your project. We are happy to help you navigate the technical side of web development.