[Writing](https://ruesandora.com/writing/) Case study

# We scanned our own site: 21 signals are open on ruesandora.com

By [Rues](https://ruesandora.com/about) · Published 29 October 2026 · Updated 29 October 2026

Sources checked on 25 October 2026

Short answer

We scanned our own site, ruesandora.com, with Ruescan on 18 October 2026: 86 out of 100, band good. Of 188 signals, 116 are solid, 21 open and 20 unmeasured. Eight open signals are security and eight are content. None blocks Google or AI bots from reaching a page. The numbers belong to the 18 October version.

Ruescan is Rueseo's site scanner. Scanning is closed to the public for now, and the [waitlist](https://ruesandora.com/#bekleme) is open. We ran it on our own site first and we publish the result as it came out. You can also read this post as a sample report: what each number says, what an open signal means, and where to start.

The scan ran on 18 October 2026. On the publication day the measurement is 11 days old. Ruescan now checks 275 signals, while the 18 October version checked 188. A fresh scan today will not match the numbers here one to one.

## Result: 86 points, band "good"

Ruescan looks at the home page, the site files (robots.txt, llms.txt, sitemap) and two sample pages picked from the sitemap. The score is a weighted average of the signals it could measure. For us the measured weight was 88%.

| Status | Signals |
| --- | --- |
| Solid | 116 (109 solid + 7 info) |
| Partial | 7 |
| Open | 21 |
| Could not be measured | 20 |
| Not applicable | 24 |
| Total | 188 |

"Not applicable" means the signal has no meaning for this site. A site without a mobile app, for example, has its app signals in this group. "Could not be measured" means a data source was unreachable, and those signals stay out of the score. How the score is calculated is explained on [how Ruescan scores](https://ruesandora.com/how-ruescan-scores).

## 15 of the 20 unmeasured signals are speed signals

Speed data comes from Google's PageSpeed service. In the environment we scanned from, the service limited keyless requests and returned 429. That left 15 of the 20 unmeasured signals empty. With an API key the share can differ, and we did not check whether the live product uses one for this post. We still count them, since an "unmeasured" row in a scan report is information too: no verdict was given on that signal.

## Which areas have the 21 open signals?

| Area | Open signals |
| --- | --- |
| Security | 8 |
| Content | 8 |
| Brain (brand and identity data) | 3 |
| Structured data | 1 |
| Speed and code | 1 |

In security the open items are the HSTS header, Content-Security-Policy, Permissions-Policy, security.txt, DMARC, a CAA record, DNSSEC and a plain-text email address on the page. In content they are a freshness date, an author byline, outbound source citations, consecutive sentences starting with the same word, few transition words, agreement between title, H1 and og:title, a quotable sentence and traces of original data.

Ruescan sorts each signal as "blocker" or "quality". Blockers are signals that stop Google or AI search bots from entering, reading or indexing a page. None of our 21 open signals is a blocker. In the AI access category, 21 of 21 signals are solid.

## What did we close in a week?

Our first internal scan on 13 October gave 85 points with 22 of 170 signals open. By 17 October we had logged 8 fixes:

- Refreshed the sitemap `lastmod` dates three times (15, 16 and 17 October).
- Added areas of expertise (`knowsAbout`) to the founder node and a brand link to the organization schema.
- Added Markdown versions of the Ruescan and scan pages, an agent section in `llms.txt` and an alternate link.
- Added `twitter:image` to every page and shortened one page's meta description.
- Moved web fonts from Google Fonts to our own server.
- Updated the `llms.txt` descriptions.

The result went from 85 to 86. We do not read meaning into one point. Two scans of the same site on the same day can differ by a few points. We show that in [three tools scored the same 10 sites](https://ruesandora.com/writing/three-tools-same-10-sites).

## What can we say about the open ones?

Our internal security review of 10 October 2026 recorded that the static site had no HSTS and no CSP. It suggested turning HSTS on from the Cloudflare setting and trying a report-only CSP first. Both were still open in the 18 October scan. For the other 19 open signals we have no written record of "left on purpose" or "not yet reached". So we do not invent reasons for them.

## How to read the report on your own site

1. Look at the open and unmeasured counts first, the score second.
2. Start with blocker-class items. A bot reaching the page comes before everything else.
3. "Not on the home page" and "not on the site" are different. Ruescan mainly looks for dates and authors on the home page.
4. If a signal does not fit your kind of site, you may leave it open. Write down why, so you do not ask in a few months whether it was on purpose.

## Frequently asked questions

### What score did ruesandora.com get?

86 out of 100 in the 18 October 2026 scan, band "good".

### How many signals does the scan have?

188 in the 18 October version. 275 in the current version.

### Can an open signal drop a site from the index?

None of our 21 open signals is in the class that blocks Google or AI bots. On another site, an open blocker-class signal is a different story.

### Why does the score move between scans?

Some signals depend on timing and on the request path. We saw a few points of difference between same-day scans and did not investigate the cause.

## Sources

- Ruescan scan of ruesandora.com, 18 October 2026 (internal record, raw output kept in-house).
- Internal scans of 13 and 17 October 2026 and the fix log (internal record).
- Internal security review of 10 October 2026 (internal record).

## Want to talk about this for your brand?

Write about your project and what you want to do. The message goes straight to Rues.

[Open the contact form](https://ruesandora.com/#iletisim)

[Email info@ruesandora.com](mailto:info@ruesandora.com) [Telegram ruesandora](https://t.me/ruesandora) [X @ruesandora0](https://x.com/ruesandora0) [Instagram @ruesandora0](https://www.instagram.com/ruesandora0) [YouTube @ruesandora0](https://www.youtube.com/@ruesandora0)

Page: https://ruesandora.com/writing/our-own-site-scan