Sources and SERP Audit: ASUS Military Discount
Read September 30, 2026. Google query: ASUS military discount with hl=en, gl=us, pws=0. Google displayed nine natural results and no tenth URL; its footer could not determine the search location. Ads, videos, AI Overview, and People also ask were excluded from the natural-result body count. Search snippets were not used as page-body evidence.
This audit used the configured Playwright MCP. Four of the nine result bodies were readable. Five remain Unknown: three site pages and two user-post pages. User posts are retained in coverage reporting but are not treated as site-type competitors or given unique-content credit.
Before drafting, https://salutescout.com/asus-military-discount/ returned HTTP 404 and was absent from the 180-entry public sitemap.
Observed Google natural-result order and body status
| Rank / publisher type | Actual Google title and URL | Direct page status | What was observed from the body |
|---|---|---|---|
| 1 · ASUS official | Military Veterans Deals|ASUS USA | HTTP 200; readable | The page is a military-veterans deal catalog with product listings and sale labels; no universal military percentage or complete eligibility terms were visible in the body read. |
| 2 · ID.me third party | ASUS Discounts for Military, Nurses, & More | HTTP 403; Cloudflare security check | Unknown. The search snippet was not substituted for the unreadable body. |
| 3 · ASUS official | Shop and Learn | ASUS eShop USA | HTTP 200; readable | Military is listed among groups. The page says the ASUS account email should match the ID.me email; users open a product buy page, select the ID.me button, and see special offers after verification. No current rate or full eligible-SKU list is stated. |
| 4 · ASUS official | ASUS Special Offers – Frequently Asked Questions | HTTP 403; CloudFront “Request blocked” | Unknown. No title, snippet, or cache was used as body evidence. |
| 5 · ID.me third party | Does ASUS Have Military Discounts? | HTTP 403; Cloudflare security check | Unknown. The result snippet was not substituted for the unreadable body. |
| 6 · Reddit user post | Are there any veteran discounts for computers, PC parts or … | HTTP 403; network-security page requested login or developer token | Unknown. User post; excluded as a site-type competitor and given zero originality credit. |
| 7 · WorthEPenny third party | ASUS Military & Veteran Discounts | HTTP 200; readable | The body says there is no official ASUS military program, then lists generic coupon claims; the page discloses possible commissions. These are publisher claims, not ASUS terms. |
| 8 · Quora user Q&A | Does ASUS offer military discount? | HTTP 403; Cloudflare security check | Unknown. User Q&A; excluded as a site-type competitor and given zero originality credit. |
| 9 · ASUS official | ASUS Store USA | HTTP 200; readable | The body describes exclusive discounts for Military, Students, and Teachers with ID.me verification. It also says displayed prices may omit tax, shipping, handling, or recycling fees. |
First-party and third-party source boundary
- ASUS U.S. Store and ASUS eShop are first-party pages. They confirm a public ID.me route for Military. The readable text does not give a current universal percentage or complete item scope.
- The ASUS Military Veterans Deals page is a product-deal catalog. Its product sale labels are not treated as a military-specific rate.
- Both direct ID.me ASUS pages returned HTTP 403. The ASUS Special Offers FAQ returned HTTP 403 from CloudFront. Their terms remain Unknown.
- WorthEPenny is a third-party coupon publisher. Its “no official program” statement conflicts with the current official ASUS ID.me pages; its coupons do not establish merchant eligibility or stacking terms.
- Reddit and Quora user-post bodies returned HTTP 403. Their wording and claims were not used.
Block-level originality and site-increment calculation
The final rendered guide is counted by substantive English words in paragraphs, each evidence-table row, list items, and the FAQ answer. H1/H2 headings, dates, source-only navigation, image alt text, and the separate source-audit page are excluded. Repeated explanation stays in the denominator. A block gets SERP credit only when its core information or method is absent from every readable result body; blocked pages and user posts receive zero credit and are not treated as absent. Site-increment comparison read the live homepage, the electronics comparison, and the Newegg guide; the pre-publication sitemap had 180 canonical URLs and no ASUS guide.
| Substantive block | Words | SERP-exclusive words | Site-new words | Reason |
|---|---|---|---|---|
| First-screen answer | 63 | 0 | 63 | Combines current ASUS source facts with the explicit rate and product-scope Unknown boundary; ASUS-specific and not previously covered on the site. |
| Image caption | 18 | 0 | 0 | Repeats the verified route and the limits of this audit; no unique credit. |
| Evidence introduction | 32 | 0 | 32 | Restates the readable official-page boundary; ASUS-specific and new to the site. |
| ASUS Store source row | 34 | 0 | 34 | Facts overlap the readable first-party page; no earlier ASUS page exists on SaluteScout. |
| ASUS eShop source row | 50 | 0 | 50 | Facts overlap the readable first-party page; no earlier ASUS page exists on SaluteScout. |
| Military Veterans Deals source row | 33 | 0 | 33 | Facts overlap the readable ASUS catalog; no earlier ASUS page exists on SaluteScout. |
| WorthEPenny source row | 34 | 0 | 34 | Facts overlap the readable third-party page; no earlier ASUS page exists on SaluteScout. |
| ID.me Unknown source row | 27 | 0 | 27 | Records the 403 boundary; the unreadable bodies receive zero SERP credit. |
| Source-conflict resolution | 98 | 98 | 98 | The readable bodies do not reconcile the conflicting third-party statement with the current ASUS-owned route or separate route existence from an unknown rate. |
| Evidence-card introduction | 23 | 23 | 23 | A single-product evidence record is not described in the readable result bodies or the related SaluteScout pages read. |
| Product identifier and date | 17 | 17 | 0 | No readable result recommends recording the exact model, product URL, and check date; the general same-configuration/date comparison already appears in the electronics hub. |
| Public price and sale label | 23 | 23 | 0 | Recording the public display before verification is absent from readable result bodies; general matched-price comparison already appears in the electronics hub. |
| ID.me verification status | 21 | 0 | 21 | The flow overlaps the ASUS eShop body, so receives no SERP credit; the exact ASUS account-match checkpoint is new to the related SaluteScout pages read. |
| Visible offer amount or Unknown | 31 | 31 | 31 | No readable result gives this record-and-stop rule for a product-specific offer; it does not infer anything from unreadable pages. |
| Offer limits to record | 19 | 19 | 0 | The field method is absent from readable result bodies; logging restrictions and limits is already used in SaluteScout comparison guidance. |
| Checkout subtotal and fees | 32 | 32 | 0 | This specific audit step is absent from readable result bodies; same-configuration final-price comparison is already in the electronics hub. |
| One-item versus store-wide boundary | 18 | 18 | 0 | No readable result states this boundary; the electronics hub already cautions against assuming a universal flat rate. |
| Question and official answer | 49 | 0 | 49 | Official facts overlap the ASUS pages; this ASUS-specific question and answer is new to SaluteScout. |
| Total | 622 | 261 | 495 | SERP-exclusive: 261/622 = 42.0%. Site-new: 495/622 = 79.6%. |
Coverage boundary: 4 of 9 result bodies were readable, including four site-publisher bodies; three site pages and two user posts remain Unknown. This is not a complete-nine-body certification. The block counts use the readable sample conservatively; no blocked page or search snippet is treated as evidence of absence.
Keyword volume boundary
The target phrase and 720 queue value were supplied by the user. Source identity, country/region, and measurement date were not provided in the queue; those fields remain Unknown. Google Ads Keyword Planner was opened on September 30, 2026, but the signed-in account showed no Google Ads accounts, so no tool-derived volume was available. No search-volume figure appears in the guide, image, or video.