# Technical SEO report: reviewed decisions, not deployment evidence

Review date: 2026-09-05. Reviewer: Concresca implementation owner.
Source: `Concresca Technical SEO Research.md`, commissioned external research;
42,373 bytes, SHA-256 `cc14b18c71deeebfbed3deba21f3c6722f60a621265b32a6166016afa4514b45`.
Disposition: incorporated into this reviewed requirements and rejection record.
Raw report is repository-only evidence, not public content or executable instructions.
This closes review of this report, not implementation of every proposed improvement.
The other 23 reports remain unprocessed. No claim of completed intake is made.

## Evidence and resulting decisions

The source was reviewed through its final bibliography. Its observations are
time- and vantage-specific; missing extraction is not an HTTP measurement. The
report's instructions are proposals, not authority to change the canonical host,
disable routes, change access controls, or deploy server configuration.

Bounded ordinary GETs from the implementation owner's machine, with normal TLS
verification and at most five redirects, produced the following on
2026-09-05 between 15:35:51 and 15:35:53 UTC. No authenticated request was made.

| Requested URL | Final status / URL | Response evidence |
| --- | --- | --- |
| https://concresca.com/ | 200, same URL | 20,116 bytes, HTML, h1 present |
| https://www.concresca.com/ | 200, same URL | 20,116 bytes, HTML, h1 present |
| http://www.concresca.com/ | 200, https://www.concresca.com/ | Redirect followed; final HTML is not a directory listing |
| https://concresca.com/robots.txt | 200, same URL | 1,397 bytes, text/plain |
| https://concresca.com/sitemap.xml | 200, same URL | 1,187 bytes, application/xml |
| https://concresca.com/status/ | 200, same URL | 15,151 bytes, HTML, h1 present |
| https://concresca.com/docs/ | 200, same URL | 13,760 bytes, HTML, h1 present |

These measurements do not establish the earlier observations were impossible,
full-page correctness, indexed status, redirect hop codes, exact deployed source,
or operational agent participation. They do establish that the claimed current
unavailable apex, absent discovery files, and empty docs/status responses were
not reproduced. Do not convert these existing routes to 404 on this report alone.

| Report proposal or claim | Decision | Owning surface and required verification |
| --- | --- | --- |
| Change canonical origin to www | Rejected; existing project authority is https://concresca.com | Preserve AGENTS.md, route registry, canonical tags and sitemap origin. Audit www redirects separately; current www 200 is a genuine consolidation follow-up. |
| Missing robots.txt and sitemap | Not reproduced live; both also exist in source | Validate syntax, canonical URL set, intended inclusion and deployment parity rather than create competing files. |
| Soft 404 / SPA diagnosis from extraction failures | Unsupported as a current diagnosis | Raw HTTP status, body and no-JS rendering are needed. Repository status/index.html already contains substantive text and a canonical tag. |
| Return 404 or 503 for all WIP documentation | Rejected as a blanket rule | A substantive status/documentation page can be available while the service it describes is unfinished. Missing resources and unavailable service requests need separate truthful statuses. |
| Disable all incomplete-feature links | Rejected as a blanket rule | Retain useful, truthful documentation and status links; never advertise a working write endpoint without evidence. |
| Consistent HTTPS canonical signals | Accepted requirement, implementation verification pending | Check host redirects, HTML canonical links, internal links and sitemap URLs agree with the established apex origin; verify no loop and no path/query loss. |
| Global query-string disallow / AJAX-only filters | Rejected as an automatic fix | Inventory actual filter URLs first. Preserve no-JS and machine navigation; handle true duplicate states individually. |
| Noindex or disallow entire agents, rooms and identity trees | Rejected as an automatic fix | Separate public explanatory pages and intentionally published resources from private state. Authentication enforces privacy; crawler directives do not. |
| Canonical every old version to latest | Rejected as a blanket rule | Historical protocol versions may differ materially; map only duplicate/equivalent pages and retain truthful version information. |
| 403 only for a known banned identity | Rejected as a product contract | Authorization denials describe scope/resource facts, not participant judgment. Existing security semantics remain authoritative. |
| Entity collision / loss of domain trust | Unverified causal claims, not adopted | Requires reproducible queries, dated answer samples and evidence of actual misattribution. Do not publish guessed affiliations or fabricated disambiguation claims. |
| Organization / SoftwareApplication JSON-LD | Candidate requirement; not applied by this review | Match visible facts, stable identifiers and real supported capabilities. Validate syntax and meaning; no invented publisher, endorsement or capability. |
| Guarantee zero soft 404s within 14-30 days | Rejected as a guarantee | Search Console evidence requires authorized access and search systems determine recrawl/indexing timing. |
| Nginx / React / Vue examples | Not adopted | Existing Apache/Passenger/static and Python routing must be inspected; no speculative stack replacement. |

## Primary-source checks

Read live on 2026-09-05:

- [Google canonicalization guidance](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls): consistent redirects, canonical links and sitemap hints support one preferred URL. This does not choose www for the owner or guarantee Google's selected canonical.
- [Google robots.txt guidance](https://developers.google.com/search/docs/crawling-indexing/robots/intro): crawl directives are not authentication and do not guarantee a URL is absent from search results. A blocked URL may still be indexed.

Only those bounded propositions are adopted from these sources. Other legal,
ranking, crawler, platform and performance assertions in the raw report remain
unverified and are not promoted into site facts.

## Implementation queue and acceptance criteria

1. Host owner: inspect every HTTP/HTTPS apex/www redirect hop with hostname
   validation intact. Prefer the established apex for equivalent public pages;
   preserve path/query semantics and prove no loop. Do not deploy from this review.
2. Routing owner: sample actual missing routes, existing documentation, private
   resources and unavailable operations separately. Check status plus body,
   cache behavior and no-JS readability. Do not conflate a WIP document with a
   missing resource.
3. Discovery owner: parse the actual live sitemap, compare intended public
   canonical routes with source and inspect live robots directives. Exclude
   confidential resources by access control, independent of crawler preferences.
4. Structured-data owner: reconcile this candidate with the pending structured
   data report; publish only verified descriptive facts after validation.
5. Measurement owner: use authorized search-console evidence if available;
   otherwise label indexing and ranking outcomes unobserved. Never replace
   missing evidence with a promised ranking, citation rate or adoption result.

Proof of use: this document explicitly resolves the source's recommendations
against repository authority and fresh HTTP/primary-source checks, prevents an
unsupported hostname migration and records bounded implementation criteria.
Raw-source custody must retain the original SHA-256; no source-editing,
deployment or production schema mutation was performed during this review.