Site profile
frenchy.es
Built with gtag, jsxgraph 1.13.3, jquery.flipster 1.1.6, @vitest/utils 5.0.2, @lanyundev/blog-static 1.4.18, @grigorov-it/mazer 2.2.0, @unhead/vue 3.4.1. 5 pages and 11 stored files, last crawled 2026-10-02.
rank 587,889 7 libraries 3 identifiers 0 third-party hosts 1 crawl open the site
Technologies and libraries
Recognised by fingerprinting the stored files and bundles against known releases; a version is the release the bytes match.
| Library | Version | Seen |
|---|---|---|
| gtag | 2026-10-02 | |
| jsxgraph | 1.13.3 | 2026-10-02 |
| jquery.flipster | 1.1.6 | 2026-10-02 |
| @vitest/utils | 5.0.2 | 2026-10-02 |
| @lanyundev/blog-static | 1.4.18 | 2026-10-02 |
| @grigorov-it/mazer | 2.2.0 | 2026-10-02 |
| @unhead/vue | 3.4.1 | 2026-09-24 |
Tracking, tag and verification IDs
Public identifiers read out of the source. Each links to every other site in the index that carries the same one.
| What | Value | Found in |
|---|---|---|
| Bing site verification (Microsoft) | C51905D3B05248B829AC864C23FEEE73 | view source |
| Facebook app id (Meta) | 1923155921341058 | view source |
| Google Analytics 4 measurement id (Google) | G-80PLDB7LE0 | view source |
Third-party hosts
The stored pages and scripts reference no host outside frenchy.es.
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
Timeline
One entry per crawl, newest first, with what changed since the crawl before: libraries, identifiers, third-party hosts and files. Historical versions stay viewable because the stored chunks are shared between versions, never copied.
-
first crawl
5 pages, 11 files, 1.7 MB; 6 libraries, 3 identifiers, 0 third-party hosts
6 libraries added
- gtag
- @vitest/utils 5.0.2
- jquery.flipster 1.1.6
- @grigorov-it/mazer 2.2.0
- jsxgraph 1.13.3
- @lanyundev/blog-static 1.4.18
3 identifiers added
- G-80PLDB7LE0 Google Analytics 4 measurement id
- C51905D3B05248B829AC864C23FEEE73 Bing site verification
- 1923155921341058 Facebook app id
11 files added
- https://frenchy.es/ html
- https://frenchy.es/blog/ html
- https://frenchy.es/google-maps-para-clinicas/ html
- https://frenchy.es/casos-de-estudio/seo-local-clinicas-dentales-madrid/ html
- https://frenchy.es/svl/ html
- https://frenchy.es/wp-content/cache/min/1/wp-con…direct-script.js?ver=1784626334 js
- https://frenchy.es/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 js
- https://frenchy.es/wp-content/plugins/wp-rocket/…/17.8.3/lazyload.min.js js
- https://frenchy.es/wp-content/plugins/wp-rocket/assets/js/wpr-beacon.min.js js
- https://frenchy.es/wp-content/cache/min/1/wp-con…/swv/js/index.js?ver=1784626972 js
- https://frenchy.es/wp-content/cache/min/1/wp-con…/js/index.js?ver=1784626972 js
Questions about frenchy.es
- How does PageSourceSearch know what frenchy.es is built with?
- From the site's own source code. The crawler stores the exact bytes of its pages and first-party scripts; the libraries are recognised by fingerprinting that code against known releases, the identifiers are read out of the tag snippets, and the third-party hosts are the script, iframe and stylesheet sources in the HTML and the absolute URLs inside the scripts. Nothing is inferred from headers or guessed.
- How far back does the history of frenchy.es go?
- To the first crawl the timeline lists. Every crawl records what the site looked like; when a file's content changes, its earlier version stays viewable because the stored chunks are never deleted, only mapped. A crawl that finds a file unchanged adds no copy.
- Can I see an older version of a script from frenchy.es?
- Yes. In the stored files list, every date under a file opens the version that was live at that crawl, with the same viewer as the current one. The raw bytes can be downloaded from there.
- Which other websites use the same tracking IDs as frenchy.es?
- Each identifier links to its reverse lookup, the list of every site in the index whose source carries the same id: the sites one analytics property or tag manager container is shared across.
Look up another site, browse sites by tracking ID, third-party host or technology. Site owners: see the crawler page for how stored pages are removed.