What Can and Cannot Be Recovered from a Public Website URL

An authorized public URL can support a high-fidelity reconstruction of what a browser receives. It cannot recover the original private repository, WordPress database, server-side PHP, admin configuration, or business logic that the public response never exposes.

This distinction matters when an original developer is unavailable, a repository was lost, or the customer controls a live site but has incomplete materials.

Usually observable from public pages

Subject to authorization, license, and access rules, a reconstruction process may inspect:

• public URL structure and navigation;
• rendered HTML and accessible text;
• CSS, fonts, colors, spacing, and responsive layout;
• public images, icons, video references, and download links;
• JavaScript and browser-visible interactions;
• forms and their visible fields, but not necessarily the private submission service;
• metadata, canonical links, robots directives, sitemaps, and structured data;
• public network requests and API responses available to an ordinary visitor.

These inputs can be reorganized into maintainable components, fresh CSS, an Astro front end, or a WordPress theme. The result is a new implementation based on the visible specification—not recovery of the original source.

Usually not recoverable from the public response alone

• original Git history, branch decisions, comments, and uncompiled components;
• WordPress posts, revisions, users, roles, settings, and database relationships;
• PHP theme/plugin code that never reaches the browser;
• private APIs, secrets, webhooks, cron jobs, email pipelines, payment logic, and admin integrations;
• members-only or role-specific behavior that the authorized test account cannot access;
• third-party source assets or licenses that the customer does not control;
• server configuration, backup history, security controls, and operational procedures.

Similar appearance is not functional equivalence

A visually close page can still lack form delivery, search, commerce, accessibility, performance, analytics, consent, localization, and content-management behavior. A reconstruction brief should list required functions separately from visual fidelity.

A responsible URL route

1. Confirm ownership or written authorization.
2. Define allowed hosts, paths, crawl rate, and excluded data.
3. Capture a manifest and evidence date.
4. Separate reusable customer assets from third-party or uncertain assets.
5. Rebuild the public experience into maintainable source.
6. Re-implement hidden functions from requirements or separately supplied materials.
7. Verify the new site rather than assuming a visual match is enough.

The WordPress Theme Handbook explains how a maintainable theme is structured; it is a more appropriate target than preserving minified deployment output as long-term source.

If you own a site but no longer control its original project, describe the URL and the result you need. The public form is only for fit review, not credentials or bulk copying.