How to Check if a Site Is WordPress

Methods to Check if a Site Is WordPress

The fastest way to check if a site is WordPress is to inspect its source code. Search for wp-content or wp-includes. These folder names often appear in links to stylesheets, scripts, and images.

Use several checks before you decide. Site owners can hide WordPress clues with security tools. They can also change login paths and remove footer credits.

Start with these checks:

• Look for WordPress names in the footer.
• Try common login paths, such as /wp-admin.
• Search the page source for WordPress folder names.
• Check the site with Wappalyzer or BuiltWith.
• Look for a WordPress RSS feed.

One clue can mislead you. Three matching clues give you far more confidence.

Inspect the Footer for WordPress Clues

Many WordPress sites show a footer credit such as “Proudly powered by WordPress.” This is the simplest check. Scroll to the bottom of the home page and inspect the footer links.

A footer credit does not prove the site still uses WordPress. A copied theme may keep old wording after a site move. Some owners also remove the credit for a cleaner design.

Check the link target if the credit is clickable. A link to WordPress.org supports the clue. Still, treat the footer as a first step, not final proof.

Try Common WordPress Login URLs

WordPress sites often use /wp-admin or /wp-login.php for sign-in. Add each path to the domain name, such as example.com/wp-admin. A WordPress login screen confirms that the site runs WordPress.

You may see a redirect to a login form. You may also see a “not found” page. That result proves little because security tools can hide or change these paths.

Do not guess passwords or send repeated login requests. You only need to view the public response. Stop if the site blocks access or shows a security warning.

Some sites send /wp-admin to a custom login path. That still creates a useful WordPress clue.

Read the Page Source

Page source inspection gives strong evidence without any special tool. Right-click the page and choose “View Page Source.” Then use your browser search to find wp-content, wp-includes, or wp-json.

The wp-content folder stores themes, plugins, and uploads. The wp-includes folder holds core WordPress files. These paths often appear in stylesheet and script URLs.

For example, a link like /wp-content/themes/sample/style.css points to a WordPress theme. A path like /wp-content/plugins/contact-form/assets.js points to a plugin folder.

WordPress can hide or rename some paths. Caching can also remove clues from the first page you view. Check two or three pages when the home page gives no answer.

What the source can reveal

• Theme paths: Find the active theme folder after /wp-content/themes/.
• Plugin paths: Find plugin names after /wp-content/plugins/.
• REST clues: Look for links that mention wp-json.
• Generator tags: Some sites expose a WordPress version in the source.

Use Browser Extensions and Technology Tools

Browser extensions can scan a page and report its likely content system. Wappalyzer can show WordPress, server tools, analytics systems, and other stack details. Its technology directory explains the systems it can detect.

BuiltWith offers another view of a site's public technology stack. Enter a domain into its lookup tool and review the results. These tools use visible code, headers, scripts, and known patterns.

Results are not always complete. A firewall may hide headers. A cache may remove script clues. Privacy tools can also hide analytics tags.

Use these tools for a quick scan. Use page source checks when you need stronger proof.

Identify Plugins and Themes

Plugin names often appear in HTML class names, asset paths, and script files. A form may use classes linked to a contact form plugin. A shop may expose paths linked to WooCommerce.

Look for clues such as plugin folder names after /wp-content/plugins/. Site behavior can help too. A product cart, image gallery, or form may point to a known WordPress plugin.

Do not treat a class name as proof. Developers can copy class names from another system. They can also combine WordPress with custom code.

Theme detector tools can often identify the active WordPress theme. They read the theme path from the source. Search the theme name on its maker’s site to confirm the match.

A child theme can make detection harder. In that case, the source may show a child theme while the design comes from a parent theme.

How to check related WordPress details

Public pages rarely reveal the exact WordPress version. Search the source for a generator tag or versioned script link. Site owners often remove both clues for safety.

You cannot reliably check site traffic or pageviews on another WordPress site. Those figures live inside private tools, such as analytics or server logs. Public estimates may come from outside data sets and can be far off.

On your own site, check pageviews in your analytics tool. Check traffic in your hosting panel or analytics report. WordPress itself does not reveal a site's full visitor count by default.

To check the PHP version on your own site, open Tools > Site Health > Info. Only site admins can view this data. The same rule applies when checking WordPress email settings.

For heavy images, review your media library and run a speed test. A performance plugin may show large files and slow requests. This is different from finding out whether a site uses WordPress.

Check WordPress RSS Feeds

WordPress creates RSS feeds by default. Try example.com/feed in the address bar. You can also try example.com/?feed=rss2.

A feed page with recent posts is a strong WordPress clue. You may see an XML response instead of a styled web page. That is normal.

Some site owners disable feeds. Others replace them with a feed service. A feed error does not rule out WordPress.

For background, see WordPress feed documentation. It covers the feed types that WordPress can publish.

Confirm the Result Without Overreaching

Combine source clues, login paths, feed checks, and tool results. A site is very likely WordPress when several checks agree.

Keep public checks separate from private site audits. You can check versions, traffic, pageviews, PHP, email, and image weight on your own site. You cannot see most of those details on a site you do not manage.

Use these checks for research, accessibility work, or migration planning. Avoid probing private areas. Respect the site's security controls.

Check	Strong clue	Limit
Page source	wp-content or wp-includes paths	Paths can be hidden
Login URL	WordPress sign-in screen	Paths can be changed
RSS feed	WordPress post feed	Feeds can be disabled
Detection tool	Matching CMS result	Scans can miss custom setups