Is this scan safe for my website?

Yes. The scan uses public website signals only. It does not ask for admin access, make production changes, crawl private areas, or test vulnerabilities.

How long does the scan take?

There is no fixed completion window. Keep this page open while the public check runs. If the browser has not updated within three minutes, retry or use the contact link for help. A completed result is also sent by email.

Do you need admin access?

No. The scan starts from the public website URL and permission confirmation. Admin, hosting, staging, database, and source-code access are outside this public-only check.

You receive a WordPress Scan result with WordPress detection, qualified theme, plugin, or page-builder traces, public response observations, limitations, and a recommended next step when the evidence supports one. Mixed evidence can produce no focused recommendation.

What information do you use?

We use public response data, public page traces, public asset paths, and headers. We do not use private credentials or customer data.

What happens after the scan?

The report can recommend a focused Technical Audit, a Decision Roadmap, direct Contact with the team, or no focused service route when the available public signals do not justify one. If a signal matters but its meaning or next action is unclear, contact the team for guidance. The Scan cannot establish a private technical root cause from public data.

Is this the same as a WordPress website audit?

A website audit normally investigates a defined technical or business scope in more depth. The WordPress Scan is a public-only triage step that reports observable signals, limitations, and the next question to confirm.

Is this a WordPress security scan?

No. The Scan does not probe vulnerabilities, test authentication, review private configuration, certify controls, or replace a security assessment. It only records public response and setup observations.

Is this a performance audit?

No. Public response observations may indicate that performance deserves follow-up, but the Scan does not run a scoped Core Web Vitals investigation, isolate bottlenecks, or promise remediation outcomes.

Is this an accessibility audit?

No. The Scan does not run an accessibility conformance audit, test representative journeys against a standard, or issue a compliance statement. Accessibility requires a separately defined review.

Does the Scan review plugin source code?

No. Public asset paths can provide qualified plugin or page-builder traces, but the Scan does not inspect proprietary plugin source, assess code quality, verify ownership, or conduct a security code review.

Get a Public WordPress Scan and a Clear Next Step

WordPress Scan

Request a public-only scan that explains visible signals and points to the right next step—without admin access.

JavaScript is required to run the WordPress Scan. Contact PathToProject if you need help choosing a roadmap path.

Public website only; no admin, hosting, database, staging, or source-code access. No payment is required. Keep this page open while the public check runs; if it does not update within three minutes, retry or use the contact link.

Queued public checkResult opens when ready

No login requiredNo access needed

Public website onlyNo private crawl

Written resultBrowser report and email

No payment requiredA public-only check

Choose the depth you need

When is the Scan enough—and when should you go deeper?

Use a Technical Audit when the technical cause is unclear, a Decision Roadmap when the business path or sequence is unclear, or direct Contact when you already know what you need or want human guidance.

You do not need to complete a Scan before contacting the team.

Use it when

WordPress Scan: You want public-only signals and a suggested next step.
Technical Audit: The technical cause, risk, or remediation boundary is still unclear.
Decision Roadmap: The business path, priorities, trade-offs, or sequence are still unclear.
Contact: You already know what you need or want human guidance before choosing a service.

Access

WordPress Scan: Public website only. No admin, hosting, database, staging, or source-code access.
Technical Audit: A focused technical question and agreed evidence, which may include approved read-only access.
Decision Roadmap: Buyer context first; deeper read-only evidence only after scope and approval.
Contact: A concise description of the project, risk, or decision; a public URL is optional for private work.

Output

WordPress Scan: WordPress detection, qualified traces, public response observations, limitations, and a next step.
Technical Audit: Evidence-backed findings about the technical cause, impact, and remediation boundary.
Decision Roadmap: Written findings, trade-offs, priorities, dependencies, sequence, and implementation boundary.
Contact: A human fit review and the most useful next conversation.

Commercial scope

WordPress Scan: No payment required. It is not implementation or a substitute for a technical audit.
Technical Audit: Paid engagement with the focused scope, price, and timing confirmed before work begins.
Decision Roadmap: Paid engagement with scope, pricing, and timing confirmed before work begins.
Contact: No payment to ask for guidance. Any paid scope is confirmed separately.

Decision	WordPress Scan	Technical Audit	Decision Roadmap	Contact
Use it when	You want public-only signals and a suggested next step.	The technical cause, risk, or remediation boundary is still unclear.	The business path, priorities, trade-offs, or sequence are still unclear.	You already know what you need or want human guidance before choosing a service.
Access	Public website only. No admin, hosting, database, staging, or source-code access.	A focused technical question and agreed evidence, which may include approved read-only access.	Buyer context first; deeper read-only evidence only after scope and approval.	A concise description of the project, risk, or decision; a public URL is optional for private work.
Output	WordPress detection, qualified traces, public response observations, limitations, and a next step.	Evidence-backed findings about the technical cause, impact, and remediation boundary.	Written findings, trade-offs, priorities, dependencies, sequence, and implementation boundary.	A human fit review and the most useful next conversation.
Commercial scope	No payment required. It is not implementation or a substitute for a technical audit.	Paid engagement with the focused scope, price, and timing confirmed before work begins.	Paid engagement with scope, pricing, and timing confirmed before work begins.	No payment to ask for guidance. Any paid scope is confirmed separately.

What the Scan can report

Sample result - illustrative only

Sample WordPress Scan

Example.com

PlatformWordPressDetected

WordPress tracesTheme, plugin, or page-builder asset hintsPublic trace

Public responseResponse and header observationsObserved

Observed public evidence: WordPress, public asset traces, and response or header observations.
What cannot be concluded: Public evidence cannot confirm ownership, business criticality, private workflows, or build scope.
Next confirming question: Are integrations, release friction, or cross-team ownership the main decision your team needs to make?
Confidence treatment: The live result states WordPress detection confidence and withholds a focused route when evidence is low or mixed.

Example route outcome, when supported: a WordPress Technical Audit. Mixed evidence can result in no focused recommendation.

Review the Technical Audit

What we cannot see

Access private areas or admin
See your database or source code
Run security or vulnerability audits
Guarantee performance or outcomes

Public evidence can tell you

Whether it's WordPress and basic version hints
Qualified theme, plugin, and page-builder traces
Public response and header observations
A recommended next step when the public evidence supports one

Possible next steps

A Scan does not assume every site needs the same paid roadmap.

The recommendation depends on the public evidence available. It can point to a focused path, a broader roadmap, or no focused recommendation until more context is available.

No focused service route

When public evidence is mixed or insufficient, the Scan can stop without recommending a focused paid service.

Ask what the evidence means

Focused Technical Audit

A focused technical question can point to an Audit when private evidence is needed to establish cause.

Review Technical Audit

Decision Roadmap

Business-path, trade-off, priority, or sequencing questions can point to a Decision Roadmap.

Compare Decision Roadmaps

Direct Contact

You can contact the team directly when the need is already clear or a public signal needs interpretation.

Discuss the project

How it works

We check what your public website reveals. You get a clear next step.

1. Submit

Submit a public website URL and confirm you are allowed to request the check.

2. Check public evidence

We inspect public responses, headers, and qualified WordPress setup traces.

3. Explain the next step

The result separates observations, limitations, and the next question to confirm.

4. Deliver the result

Keep this page open for the browser result; a completed result is also sent by email.

FAQ

Frequently Asked Questions

Public-only first step

Ready to request the WordPress Scan?

Public website only; no private access, vulnerability testing, or source-code review. No payment is required. Keep this page open while the check runs; a completed result is also sent by email.

No login or admin accessRetry or contact us if the page has not updated within three minutes

Start WordPress Scan

Public-only check. Written next step.

The scan reviews public website observations and recommends a next step. It does not include implementation scope, private access, or a vulnerability assessment.

Public-only Scan scopeNo implementation is included in this public check

Written judgment firstClarity over implementation

No admin accessWe use the public website only