Issues

What the console has found that someone should act on, each with the ticket text ready to paste. Nothing here files anything — it writes the words, you decide where they go.

Critical
4
worth acting on now
Open
7
across all businesses

www.we-pdf.com publishes no readable sitemap

PDF SaaS · www.we-pdf.com
Critical

Returns HTTP 200 with content-type text/html — it serves the app shell, not XML. Google cannot read it and neither can this page.

Ticket text
www.we-pdf.com | Sitemap does not return XML
# Bug


www.we-pdf.com serves a sitemap that cannot be parsed. Returns HTTP 200 with content-type text/html — it serves the app shell, not XML. Google cannot read it and neither can this page.

Google reads this file to discover pages, so anything only reachable through it
is invisible to search. The Live URL Console cannot list this domain either,
which means QA cannot tell a broken page apart from an unpublished one here.


In short, make www.we-pdf.com/sitemap.xml return valid XML.


**Steps to Reproduce:** open https://www.we-pdf.com/sitemap.xml

**Actual result:** Returns HTTP 200 with content-type text/html — it serves the app shell, not XML. Google cannot read it and neither can this page.

**Expected result:** valid XML listing the pages published on this host.


# Acceptance Criteria

- [ ] https://www.we-pdf.com/sitemap.xml returns XML with a content-type of application/xml
- [ ] Every URL it lists is on www.we-pdf.com and returns 200
- [ ] The other brand sitemaps are unchanged


## QA Testing

No payment needed. Open the sitemap in a browser and confirm it renders as XML rather than the app. Check one listed URL loads.

check-in.my-trip-online.com publishes no readable sitemap

Airport Check-In · check-in.my-trip-online.com
Critical

Returns HTTP 500. The host is live and took 621 ad clicks in the last 30 days, but its sitemap errors.

Ticket text
check-in.my-trip-online.com | Sitemap does not return XML
# Bug


check-in.my-trip-online.com serves a sitemap that cannot be parsed. Returns HTTP 500. The host is live and took 621 ad clicks in the last 30 days, but its sitemap errors.

Google reads this file to discover pages, so anything only reachable through it
is invisible to search. The Live URL Console cannot list this domain either,
which means QA cannot tell a broken page apart from an unpublished one here.


In short, make check-in.my-trip-online.com/sitemap.xml return valid XML.


**Steps to Reproduce:** open https://check-in.my-trip-online.com/sitemap.xml

**Actual result:** Returns HTTP 500. The host is live and took 621 ad clicks in the last 30 days, but its sitemap errors.

**Expected result:** valid XML listing the pages published on this host.


# Acceptance Criteria

- [ ] https://check-in.my-trip-online.com/sitemap.xml returns XML with a content-type of application/xml
- [ ] Every URL it lists is on check-in.my-trip-online.com and returns 200
- [ ] The other brand sitemaps are unchanged


## QA Testing

No payment needed. Open the sitemap in a browser and confirm it renders as XML rather than the app. Check one listed URL loads.

5 themes are marked active but their traffic has stopped

Top Up, Airport Check-In, eSIM
Critical

tu_halloween, tu_halloween_eur, tu_lov_it, ac_v2, _esim_eur. Each is still active = true in global-api, so nothing was switched off there. Volume against four weeks ago is at or near zero.

Ticket text
Top Up | 5 themes stopped receiving traffic while still marked active
# Investigation


5 themes have gone to roughly zero applications while remaining active = true
in global-api: tu_halloween, tu_halloween_eur, tu_lov_it, ac_v2, _esim_eur.

Nothing in our own data turned them off, so the cause is upstream — a campaign
paused, an account change, or an acquiring or compliance action on those
country and entity pairs. In September the same shape cost Top Up about 26% of
its sessions before anyone noticed, and it went unnoticed for three weeks.


In short, find out why these themes stopped and either restore them or mark them inactive.


# Acceptance Criteria

- [ ] Each theme is confirmed either deliberately stopped or restored to traffic
- [ ] Any theme that is deliberately stopped is set to active = false in global-api
- [ ] The reason is recorded on this ticket so the next occurrence is recognisable


## QA Testing

No payment needed. This is a data and account check, not a page test.

50 ad URLs serve another brand's identity on this host

checkin.my-trip-online.com
Critical

design=my-pro-travel and design=travibly running on checkin.my-trip-online.com. GP-570 removed this parameter after the same shape served one legal entity's identity on another's domain and Google suspended the ads landing there.

Ticket text
Ads | 50 final URLs carry a cross-brand design parameter
# Bug


50 live ad URLs carry a design parameter naming a brand other than the
host they run on: design=my-pro-travel and design=travibly on checkin.my-trip-online.com.

GP-570 removed that parameter after exactly this shape served one legal
entity's identity on another entity's domain, and Google suspended the ads
landing there. These URLs are still in the account.


In short, confirm each cross-brand design is intended, or point the ad at the matching host.


**Steps to Reproduce:** open any affected URL, for example https://checkin.my-trip-online.com/en/airasia/v2-no-logo?design=my-pro-travel&theme=mpt_lov

**Actual result:** checkin.my-trip-online.com renders the my-pro-travel brand.

**Expected result:** the host and the brand it presents agree, or the exception is documented.


# Acceptance Criteria

- [ ] Every cross-brand design URL is reviewed and either corrected or recorded as intended
- [ ] No ad presents one legal entity's identity on another entity's domain
- [ ] Ads that already match their host are untouched


## QA Testing

Open two or three affected URLs and check which brand the page presents. Fresh tab between cases — theme and design stick in session storage.

4 ad URLs point at pages that appear in no sitemap

checkin.my-trip-online.com
Important

/en/vola, /en/choose-airline. The ads are live and spending; the page behind them is not published for search.

Ticket text
Ads | 4 live ad URLs land on pages missing from the sitemap
# Task


4 Google Ads final URLs land on pages that no
sitemap lists: /en/vola, /en/choose-airline.

Either the page should be published and is not, or the ads should not point
there. Neither source finds this alone — the sitemap does not know what the ads
target, and the ads do not know what is published.


In short, decide whether /en/vola and /en/choose-airline should be in the sitemap, then make the two agree.


# Acceptance Criteria

- [ ] Each path is either added to the sitemap or removed from the ad
- [ ] The pages still return 200 for anyone already holding the link
- [ ] No other ad URL is changed


## QA Testing

No payment needed. Open each URL and confirm it loads, then check the sitemap lists it.

3 pages on www.we-pdf.online return 4xx

PDF SaaS · www.we-pdf.online
Important

Found by the site audit 76 days ago, across 200 pages crawled. For example https://www.we-pdf.online/en/contrat-bail-non-meuble, https://www.we-pdf.online/en/cerfa-13406-15, https://www.we-pdf.online/en/w9.

Ticket text
www.we-pdf.online | 3 pages return 4xx
# Bug


The site audit found 3 pages on www.we-pdf.online returning a 4xx, out of
200 crawled, 76 days ago.

Examples:
- https://www.we-pdf.online/en/contrat-bail-non-meuble
- https://www.we-pdf.online/en/cerfa-13406-15
- https://www.we-pdf.online/en/w9

Confirm each is still broken before acting — the audit is not live.


In short, make these pages return 200 or stop publishing them.


**Steps to Reproduce:** open any URL above

**Actual result:** 404

**Expected result:** the page loads, or the URL is removed from the sitemap.


# Acceptance Criteria

- [ ] Each URL either returns 200 or is removed from the sitemap
- [ ] Pages that already worked are unchanged
- [ ] A re-run of the audit shows zero broken pages for this host


## QA Testing

No payment needed. Open each URL and confirm it loads.

11 pages on topup-mobile.co return 4xx

Top Up · topup-mobile.co
Important

Found by the site audit 76 days ago, across 200 pages crawled. For example https://topup-mobile.co/en/diaspora/uk, https://topup-mobile.co/nl/diaspora/uk, https://topup-mobile.co/fr/diaspora/uk, https://topup-mobile.co/es/diaspora/uk.

Ticket text
topup-mobile.co | 11 pages return 4xx
# Bug


The site audit found 11 pages on topup-mobile.co returning a 4xx, out of
200 crawled, 76 days ago.

Examples:
- https://topup-mobile.co/en/diaspora/uk
- https://topup-mobile.co/nl/diaspora/uk
- https://topup-mobile.co/fr/diaspora/uk
- https://topup-mobile.co/es/diaspora/uk
- https://topup-mobile.co/it/diaspora/uk
- https://topup-mobile.co/de/diaspora/uk
- https://topup-mobile.co/ro/diaspora/uk
- https://topup-mobile.co/pt-BR/diaspora/uk

Confirm each is still broken before acting — the audit is not live.


In short, make these pages return 200 or stop publishing them.


**Steps to Reproduce:** open any URL above

**Actual result:** 404

**Expected result:** the page loads, or the URL is removed from the sitemap.


# Acceptance Criteria

- [ ] Each URL either returns 200 or is removed from the sitemap
- [ ] Pages that already worked are unchanged
- [ ] A re-run of the audit shows zero broken pages for this host


## QA Testing

No payment needed. Open each URL and confirm it loads.

These are derived from the current snapshot, so an issue disappears when the thing behind it is fixed rather than when somebody remembers to delete it. Effort and severity are a starting point, not a decision.