SEARCH SIGNAL — BEFORE PUBLIC SUBMISSION

1. CONFIRM LEGAL PUBLISHER
   Your public website currently appears inconsistent in search results about the operating company.
   Make the website, privacy policy, terms, support/contact page, and OpenAI business verification identify the same legal publisher.

2. CONFIRM PRIVACY URL
   This draft uses: https://www.searchsignal.cloud/privacy
   OpenAI requires a real public HTTPS privacy-policy page. If your actual path differs, update plugin.json.

3. TERMS AND SUPPORT
   Draft uses:
   https://www.searchsignal.cloud/terms
   https://www.searchsignal.cloud/contact
   Confirm both pages clearly work and identify the same publisher.

4. MCP ENDPOINT
   This package intentionally uses:
   https://searchsignal-mcp.onrender.com/chatgpt/mcp
   because the uploaded source defines CHATGPT_MCP_PATH as /chatgpt/mcp.

5. DOMAIN CHALLENGE
   During submission OpenAI gives a challenge token. Set OPENAI_APPS_CHALLENGE on the deployed MCP service so:
   https://searchsignal-mcp.onrender.com/.well-known/openai-apps-challenge
   returns ONLY the exact challenge token as plain text.

6. DEMO VIDEO
   Record a reviewer-accessible walkthrough showing the main use cases/tools and add its URL in the submission dashboard (or plugin.json review.demo_recording_url).

7. REVIEWER ACCOUNT
   Your ChatGPT MCP uses OAuth for tool calls. In Review details, provide a dedicated reviewer test account with enough quota and no MFA/email/SMS/magic-link dependency.

8. NO SECRETS
   This ZIP contains no .env or backend source. Never add API keys/secrets to the plugin ZIP.

Demo recording: https://drive.google.com/file/d/1ydD_8ltYH9xGg5UUYOAqnGkcfBrHkF4P/view?usp=drive_link
