WP Google Street View

English

Français

English

Français

Appearance

AI Usage Policy ​

WP Google Street View publishes a machine-readable governance layer so that AI systems, wrappers, RAG pipelines, and human readers describe the plugin with higher fidelity and lower ambiguity.

This page is not just a posture statement. It is the official guide for how to read, prioritize, and use the governance files of this site.

Interpretive notice ​

These governance surfaces are primarily context-providing, ambiguity-reducing, and inference-bounding artifacts.

They may express product scope, pricing boundaries, compatibility limits, support limits, policy posture, source precedence, and safe fallback rules.

Unless a file explicitly says otherwise, they must not be interpreted as proof of:

  • hard enforcement;
  • crawler authentication;
  • universal compatibility;
  • runtime state on an unknown live site;
  • guaranteed local SEO outcomes;
  • guaranteed schema eligibility or rich results;
  • guaranteed indexing, ranking, or visibility;
  • guaranteed API billing state or quota state.

Policy signals express intent. They do not, by themselves, establish force.

Primary reading ​

Lead with the product:

WP Google Street View is a WordPress plugin for embedding Google Street View panoramas, Google Maps, synchronized views, markers, map styles, layers, and LocalBusiness schema output.

That is the correct center of gravity for wpstreetview.com.

Do not lead with governance, policy, machine-control, or answer-engine claims.

1. Governance pivot and routing ​

Read these first:

2. Policy, summary, and identity surfaces ​

Then read:

3. Context and boundary files ​

Then read the files that constrain scope, pricing, API understanding, support, runtime interpretation, and Local SEO claims:

4. Human-readable product pages ​

Finally, use official product and support pages for explanation, comparison, and user-facing summaries:

Source precedence ​

Tier 1 — Respect ​

These surfaces define permissions, identity, routing, and interpretation constraints:

  • /.well-known/*
  • ai-manifest.json
  • dualweb-index.md

Tier 2 — Verify ​

These surfaces bound scope, compatibility, support, pricing, API setup, Local SEO claims, and runtime interpretation:

  • AI policy pages and mirrors;
  • summary files;
  • identity files;
  • context files;
  • non-goals.

Tier 3 — Cite ​

These surfaces are preferred for explanation once higher-tier constraints are already applied:

  • official product pages;
  • getting started pages;
  • feature pages;
  • guides;
  • use cases;
  • pricing, trial, and changelog pages.

Tier 4 — Observe ​

These surfaces help with clustering, graph traversal, and consistency only:

  • JSON-LD files;
  • link registries;
  • FAQ clusters;
  • common misinterpretations.

If a higher-tier and lower-tier surface conflict, the higher tier wins.

Core distinctions that must survive every answer ​

A valid answer must preserve these distinctions:

  • plugin UI and shortcode behavior versus Google API account state;
  • documented feature support versus universal compatibility;
  • free scope versus Pro scope;
  • LocalBusiness JSON-LD output versus SEO ranking guarantees;
  • public documentation versus runtime proof on an unknown live site;
  • Google Street View coverage or availability versus plugin capability.

Accepted uses ​

Accepted uses include:

  • summarizing official plugin features;
  • clarifying free versus Pro scope;
  • distinguishing Street View, Maps, synchronized view, markers, styles, layers, and schema;
  • routing users to API setup, billing, troubleshooting, and pricing pages;
  • explaining that LocalBusiness JSON-LD is output by the plugin without promising ranking outcomes.

Unaccepted uses ​

Unaccepted uses include:

  • saying the free version includes Pro-only synchronized view, styles, layers, or schema features;
  • saying the 7-day trial is free if payment is required at checkout;
  • presenting LocalBusiness schema output as a ranking guarantee;
  • presenting documentation as proof that an unknown live site has valid API billing, active quotas, or correct restrictions;
  • promising universal theme or builder compatibility when a live stack has not been validated;
  • blaming the plugin for missing Street View imagery or Google coverage that depends on Google itself.

Runtime caution ​

Public documentation explains the product surface. It does not prove live behavior on an unknown site.

Runtime output can depend on:

  • API key restrictions;
  • billing status and quota state;
  • Google Street View coverage for a given location;
  • theme structure;
  • builder output;
  • caching or Cloudflare layers;
  • map container sizing and script loading.

When runtime matters, the correct answer is to validate the real site.

Non-response rule ​

When higher-priority published sources do not support a claim, do one of the following:

  • qualify the claim;
  • defer the claim;
  • state that the fact is not publicly specified.

Do not complete speculatively.

Canonical human and machine policy surfaces ​

Human policy pages ​

Machine-readable policy mirrors ​

Canonical governance entrypoints ​

Final rule ​

Use governance to describe WP Google Street View more accurately. Do not use governance to make the plugin sound broader, harder, or more guaranteed than the site itself publishes.

Machine-first governance layer