Contact

Email

Send feedback, corrections, source suggestions, partnership notes, or SaaS GEO workflow questions to feiyangkl3@gmail.com. CiteKit is maintained as a small independent tool site, so email is the primary contact channel while the product remains static and browser-based.

Before sending feedback

The most useful messages are tied to a public page and a specific workflow. If you are reporting a tool issue, include the CiteKit URL, what you entered, what output looked wrong, and the source or page fact that should change the result. If the issue involves a private SaaS page, remove secrets and send only the public pattern needed to reproduce the problem.

• Include one CiteKit URL per issue so the fix can be traced.
• Quote the exact sentence, table row, schema field, prompt, or generated recommendation that needs review.
• Attach public documentation when the correction depends on crawler, schema, advertising, or platform policy guidance.
• Avoid screenshots that expose customer data, private analytics, passwords, contracts, or unreleased roadmap details.

Corrections

If a guide, source note, prompt example, crawler reference, schema recommendation, or tool output is inaccurate, include the page URL, the specific sentence or generated field, and a public source that supports the correction. Useful corrections are applied to the content or tool logic rather than handled as cosmetic date changes.

Correction request format

A strong correction request includes four details: the CiteKit URL, the exact text or generated output that appears wrong, the public source that supports the correction, and the impact on the workflow. For example, a crawler naming change should identify the affected crawler directory row and the official source page, while a schema correction should identify the field and the visible page claim it should match.

What to include in a useful message

For product feedback, include the workflow you were trying to complete, the page you used, and the output you expected. For crawler or schema issues, include the robots.txt rule, page head markup, or validator message if you can share it. Do not send passwords, private customer data, unreleased product information, or confidential analytics exports.

What not to send

Do not send passwords, customer lists, private analytics exports, confidential contracts, unreleased product roadmaps, personal data, or legal accusations that cannot be reviewed from public sources. CiteKit is designed around public SaaS marketing pages and documentation. If a private detail is needed for your own audit, keep it in your internal report and share only the public pattern that needs a tool or content fix.

Advertising review

CiteKit is designed to become advertising-supported after approval, but ads should stay separate from Generate, Copy, Download, Save, checklist, and log-builder controls. If an ad placement later appears confusing, too close to a tool action, or inconsistent with a page task, report the URL, screen size, and nearby control so the placement can be reviewed or removed.

Report an advertising issue

Advertising feedback should describe the exact page state because placement risk depends on context. Include the URL, device width, whether a generated result was visible, and which control appeared near the ad. A placement should be reviewed if it could be mistaken for a tool action, if it interrupts a copy or download flow, or if it makes the page less useful without adding value to the task.

• Report ads near Generate, Copy, Download, Save, checklist, log-builder, or navigation controls.
• Report any ad label, size, or position that makes the ad look like CiteKit content.
• Report blank ad boxes or placeholder wording during review periods.
• Report pages where advertising distracts from source notes, limitations, or report review steps.

Response expectations

Messages are reviewed manually. CiteKit cannot provide legal, financial, or guaranteed ranking advice, and it cannot promise ChatGPT, Perplexity, Google AI Overview, or AdSense outcomes. The best use of contact is to improve public workflows, correct inaccurate claims, and identify examples that would make the tools more useful. If a message requires private consulting or access to confidential data, it may be declined.

Expected response scope

A response, when provided, will usually focus on whether the site should change. CiteKit may update a tool rule, add a limitation, fix a source note, clarify a privacy statement, or remove a confusing advertising placement. It will not guarantee a SaaS ranking result, promise a citation in an AI answer, review confidential data, or provide legal advice about advertising, privacy, or competitor claims.