SERVICE TERMS · DRAFT

Terms

Pre-launch draft for review. There is no active paid service or checkout. Legal operator, effective date, governing law, dispute process, and delivery deadline remain pending. This draft must be completed before sales open.

1. Current stage

SEO Change Monitor is in development. This website is a product explanation and fixed-data demo. It does not perform monitoring, send alerts, take payments, or offer an active trial. No feature shown in a sample should be treated as an available service.

2. Local prototype and future terms

A local prototype checks public HTML robots/googlebot meta tags and applicable X-Robots-Tag response headers, saves results, schedules rechecks, creates English change-notification previews, and provides private status and stop controls. Emails are not delivered to real inboxes.

No package is on sale. Pricing, URL allowance, service duration, and activation deadline must be agreed before any future purchase. The prototype stores a configuration snapshot for each request and calculates the service end time from operator activation. It stops scheduled checks at that time. There is no automatic billing, renewal, or upgrade.

Canonical, HTTP-status, and redirect-change alerts are not implemented. The public demo’s canonical scenario is an illustration of a future concept.

3. Authorized use

You would only be allowed to submit a public page you own or are authorized to manage. Do not submit private network addresses, authentication links, secrets, or pages requiring a login. The planned early version does not render JavaScript, crawl whole sites, bypass access controls, or edit websites.

4. What a result means

A result would describe what the checker could observe at a particular time and with its stated request settings. The absence of a noindex directive does not prove that a page can or will be indexed. Results do not report Google’s actual index, guarantee rankings, or replace your own review.

Timeouts, access blocks, and other failed checks would be recorded as unknown, not treated as confirmed noindex changes. Periodic checks can miss changes between runs. The service would need to state how delays and email-delivery failures are handled before launch.

5. Payments, refunds, and stopping

No payment provider API or payment link is connected. A local operator command can record a manually verified goods-and-services payment and activate a request; customers cannot activate it themselves. Commercial suitability of the operator’s payment account is not yet confirmed. Before any future payment, the operator must state the total price, currency, tax treatment, scope, duration, delivery deadline, support contact, and final refund policy. Stopping monitoring does not submit or execute a refund.

6. Data and support

See the Privacy draft for current preview behavior and planned data use. The legal operator and real support details must be provided on the Contact page before the paid service is offered.

7. Items requiring operator review

Before publication, the operator must complete the parties’ legal identities, applicable law, dispute process, proportionate liability terms, any mandatory consumer rights, effective date, data-processing obligations, and the final delivery and support commitments. This draft does not claim legal or payment-platform approval.