how can you tell if a website is built in wordpress

Learn how can you tell if a website is built in wordpress by checking source code, file paths, and admin login pages. A practical guide for developers.

Eptekhar Hasan9 min read
Illustration for how can you tell if a website is built in wordpress

You can identify a WordPress site by inspecting the page source for specific file paths, checking for the wp-login.php page, and looking for unique CSS or JavaScript filenames. Most commercial sites expose these markers in the HTML head or footer sections. You do not need advanced tools to find them. You only need a browser and basic knowledge of how to view source code. This method works for any public website.

How can you tell if a website is built in wordpress?

The fastest way to confirm a site runs on WordPress is to view the page source. Press Control and U on Windows, or Command and Option and U on Mac. Look for links in the head section. If you see paths ending in /wp-content/themes/ or /wp-content/plugins/, the site uses WordPress. These folders are unique to the WordPress core structure. You will also find script tags referencing jquery.js or wp-embed.min.js. These are standard files loaded by default in most themes.

Another quick test is to type the website address followed by /wp-login.php in your browser address bar. If a login page appears with a "Password Lost?" link and a form for username and password, the site is almost certainly WordPress. This login page is the default authentication endpoint for the platform. Some site owners hide this page using security plugins, but it remains a strong indicator if present.

Inspecting the HTML source code

The HTML source contains the clearest evidence. Open the developer tools in your browser. On Chrome, press F12 or right-click and select Inspect. Switch to the Elements tab. Use the search function (Control and F in the dev tools) to search for "wp-content".

You will likely see paths like this:

<link rel='stylesheet' id='theme-css' href='https://example.com/wp-content/themes/astra/assets/css/main.min.css' type='text/css' media='all' />

The string /wp-content/themes/ is the directory where WordPress stores its themes. No other major CMS uses this exact structure. You will also see /wp-includes/ paths. For example:

<script type='text/javascript' src='https://example.com/wp-includes/js/jquery/jquery.min.js'></script>

This path points to the core WordPress include directory. If you see both /wp-content/ and /wp-includes/ in the source, you can confirm the site is WordPress. These paths are hard-coded into the platform and do not change unless a developer manually rewrites them, which is rare.

Checking for default WordPress files

WordPress ships with several default files that remain active on most sites. Check for these specific files in the source code or by navigating to their URLs directly.

  1. wp-login.php: The standard login page. Navigate to https://example.com/wp-login.php. If it loads, the site is WordPress.
  2. wp-json/: The REST API endpoint. Navigate to https://example.com/wp-json/. If you see a JSON object with a "name" field and a "url" field, the site exposes the WordPress REST API. This is enabled by default.
  3. wp-comments-post.php: The comment submission endpoint. This file handles form submissions for comments. You may not see it in the HTML, but it is part of the core.
  4. xmlrpc.php: The XML-RPC interface. Navigate to https://example.com/xmlrpc.php. If you receive a response like "405 Method Not Allowed" or similar, the file exists and is active.

The presence of wp-json/ is particularly telling. The WordPress REST API is a robust feature that allows programmatic access to site data. Many plugins and themes rely on it. If the endpoint is open, it confirms the underlying architecture.

Identifying theme and plugin fingerprints

While the core paths confirm WordPress, the specific theme and plugins reveal more about the site's configuration. In the HTML head, look for stylesheet links. The file name often includes the theme name. For example:

<link rel='stylesheet' href='/wp-content/themes/elementor/assets/css/frontend.css'>

This tells you the site uses the Elementor theme or plugin. Similarly, you will see plugin stylesheets:

<link rel='stylesheet' href='/wp-content/plugins/woocommerce/assets/css/woocommerce.css'>

This indicates the site uses WooCommerce for e-commerce. You can compile a list of active plugins by scanning all link and script tags for /wp-content/plugins/. This list helps you understand the site's functionality and potential security surface.

Common plugins that leave distinct fingerprints include:

  • Yoast SEO: Look for meta tags with the prefix "Yoast SEO" or scripts from /wp-content/plugins/wordpress-seo/.
  • WooCommerce: Look for cart and checkout scripts from /wp-content/plugins/woocommerce/.
  • Elementor: Look for data- attributes in the HTML body and styles from /wp-content/plugins/elementor/.
  • Contact Form 7: Look for forms with class names like wpcf7-form.

These fingerprints are useful if you are researching a competitor or planning a migration. They show exactly which tools the site relies on.

Using browser developer tools for deeper analysis

The developer tools go beyond static source inspection. Open the Network tab in your browser developer tools. Refresh the page. You will see a list of all resources loaded by the page. Filter the list by "Doc", "CSS", "JS", or "Img".

Look for requests to /wp-admin/ or /wp-includes/. Even if the page is public, the browser may load assets from these directories. For example, a theme might load a JavaScript file from /wp-includes/js/wp-embed.min.js. This confirms the WordPress core is active.

You can also check the Response Headers for any request. Right-click a request in the Network tab and select "Copy" then "Copy response headers". Look for headers like X-Powered-By. Some servers expose the PHP version or WordPress version here. However, many hosts hide this header for security reasons. If you see X-Powered-By: PHP/8.1, it suggests a PHP environment, which is standard for WordPress.

Another technique is to inspect the Console tab. WordPress often logs JavaScript errors or debug information here. If you see errors referencing wp-*.js files, it confirms the framework. Some plugins also output debug logs to the console. This can reveal plugin names and versions.

Verifying with the REST API

The WordPress REST API provides a structured way to confirm the platform and gather metadata. Navigate to https://example.com/wp-json/wp/v2/users. If the site allows public access to user data, you will see a JSON array of user objects. Each object includes fields like id, name, slug, and avatar_urls.

If the response is a 401 Unauthorized or 403 Forbidden error, the API is protected but still active. This is common on sites that restrict user enumeration. The error message itself often references the WordPress REST API. For example:

{
  "code": "rest_forbidden_context",
  "message": "Sorry, you are not allowed to do that."
}

This specific error code and message structure is unique to the WordPress REST API. It confirms the site runs on WordPress even if the user list is hidden.

You can also query specific post types. Navigate to https://example.com/wp-json/wp/v2/posts. If the site has public blog posts, you will see a list of them with metadata like title, content, and author. This endpoint is open by default on most installations.

Common pitfalls and false positives

Not every site with /wp/ in the URL is WordPress. Some developers use custom permalinks that mimic WordPress structures. However, the combination of /wp-content/ and /wp-includes/ is extremely rare outside of WordPress. If you see only one of these paths, investigate further.

Another pitfall is caching. If the site uses a strong caching plugin, the HTML source might be a cached version that does not reflect the current state. However, the core file paths remain consistent. Caching does not remove the /wp-content/ references because they are essential for loading styles and scripts.

Some sites use headless WordPress. In this setup, the frontend is built with JavaScript frameworks like React or Vue.js, while the backend is WordPress. In this case, the HTML source might not contain /wp-content/ paths because the content is loaded dynamically via the REST API. To detect headless WordPress, check the Network tab for requests to /wp-json/. If you see API calls to WordPress endpoints, the site is using WordPress as a headless CMS.

Why this matters for business and developers

Knowing the technology stack of a website is useful for several reasons. If you are a developer, it helps you understand how to interact with the site. If you are a business owner, it helps you evaluate the maintainability and security of your current site. If you are considering a new website, knowing that many competitors use WordPress can inform your decision.

WordPress powers a large portion of the web due to its flexibility and plugin ecosystem. It is not just for blogs. It is used for e-commerce, portfolios, corporate sites, and membership platforms. Understanding how to identify it helps you recognize its prevalence and capabilities.

If you are looking to build a site that is easy to maintain and has a large developer community, WordPress is a strong choice. It offers a balance of control and accessibility. However, it requires regular updates and security monitoring. If you are not technical, you might prefer a managed solution.

For local businesses, a well-built WordPress site can handle complex needs like booking systems, blogs, and online stores. The key is choosing the right theme and plugins. If you are unsure about the technical setup, consider working with a specialist who can configure the site correctly from the start. You can learn more about how we approach building robust, maintainable sites for local businesses in our guide to local business websites.

Summary of detection methods

To recap, use these methods in order of reliability:

  1. View Source: Look for /wp-content/ and /wp-includes/ paths.
  2. Login Page: Check if /wp-login.php exists.
  3. REST API: Query /wp-json/ to see if the API is active.
  4. Network Tab: Inspect loaded resources for WordPress-specific files.
  5. Plugin Fingerprinting: Identify specific plugins via CSS and JS file names.

These methods are non-invasive and do not require access to the site's backend. They rely on public information that the site exposes to all visitors. By combining these checks, you can confirm with high confidence whether a site is built on WordPress.

The process is straightforward once you know what to look for. It takes less than a minute to check the source code and a few minutes to verify the API endpoints. This knowledge is valuable for developers, marketers, and business owners alike. It helps you make informed decisions about technology choices and competitive analysis.

If you are planning a new project, understanding the landscape of available platforms is the first step. WordPress remains a dominant choice due to its open-source nature and extensive library of extensions. Whether you are migrating an existing site or building from scratch, knowing how to identify the platform helps you plan your approach.

For more insights on web technologies and how they impact business operations, check out our other articles on web development trends and digital marketing strategies. These resources provide a broader context for understanding the tools that power modern websites.

Remember that technology stacks evolve. New plugins and themes are released regularly. However, the core structure of WordPress remains consistent. The paths /wp-content/ and /wp-includes/ are fundamental to the platform and are unlikely to change. This stability makes identification reliable over time.

By mastering these detection techniques, you gain a practical skill that applies to any website you encounter. It is a useful tool for due diligence, competitive research, and technical planning. The ability to quickly identify the underlying technology saves time and reduces uncertainty.

If you have questions about specific sites or need help with your own project, consider reaching out to a professional. You can visit our contact page to discuss your needs. We provide clear, honest advice on technology choices and implementation. Our goal is to help you build a site that works for your business, not just for search engines.

Understanding how to tell if a website is built in WordPress is a foundational skill in web development. It opens the door to deeper analysis and informed decision-making. Use the methods described in this guide to verify the platform of any site you are researching. The process is simple, effective, and widely applicable.

Keep reading

All guides