Hotelipp
Hotelipp（ホテリップ） は、旅行ブロガーやアフィリエイターのためのWordPressプラグインです。ホテルのアフィリエイトリンクカードを簡単に作成・管理できます。 Hotelipp is a WordPress plugin for travel bloggers and affiliate marketers that makes it easy to create and manage hotel affiliate link cards. 楽天トラベルAPIを使って管理画面から直接ホテルを検索し、ワンクリックでリンクカードを記事に挿入できます。 Search for hotels directly within the plugin using the Rakuten Travel API, and insert beautiful link cards into your posts with a single click. 詳しくは https://hotelipp.com/ をご覧ください。 For more details, visit https://hotelipp.com/ 対応アフィリエイトサービス / Supported Affiliate Services 楽天トラベル — Rakuten Travel (Rakuten Affiliate / Moshimo Affiliate) じゃらん — Jalan (ValueCommerce) るるぶトラベル — Rurubu Travel (ValueCommerce) Yahoo!トラベル — Yahoo! Travel (ValueCommerce) 一休.com — Ikyu.com (ValueCommerce) Agoda (Agoda Partner Program) 追加予約サイト（設定で個別に有効化） / Optional Booking Sites JTB (ValueCommerce) 近畿日本ツーリスト — Kinki Nippon Tourist (ValueCommerce) 東海ツアーズ — Tokai Tours ゆこゆこネット — Yukoyuko (ValueCommerce) Relux (ValueCommerce) HIS (ValueCommerce) 主な機能 楽天トラベルAPIによるホテル検索＆ワンクリック登録 ホテルの最低価格及びレビュー内容の自動更新（常に最新の状態を保持） 一元化されたアフィリエイトID管理 — 一度設定すれば、すべてのリンクに自動的に適用されます Gutenbergブロックエディター対応 ショートコードによるクラシックエディターへの対応 ボタンの順序・色がカスタマイズ可能 レスポンシブデザイン — モバイルではボタンが1列に並ぶ オリジナル画像を使ったホテルカードの作成も可能 Acknowledgements / 謝辞 This plugin’s design and UI were inspired by the excellent WordPress plugin “Pochipp”. We are grateful to its author. 本プラグインのデザイン・UIは、優れたWordPressプラグイン「ポチップ」に着想を得ています。作者の方に感謝します。 External Services This plugin connects to the following external services. Rakuten Web Service (Rakuten Travel API) Used to search for hotels and retrieve hotel information (name, price, review score, image). A Rakuten Developer account is required. Data is sent to Rakuten servers when the user performs a hotel search, when WP Cron runs a scheduled update, or when the site administrator runs a connection test on the plugin’s API diagnosis page. * Website: https://webservice.rakuten.co.jp/ * Terms of Service: https://webservice.rakuten.co.jp/guide/rule * Privacy Policy: https://privacy.rakuten.co.jp/ Rakuten Travel (hotel page link check) Used to check whether a registered hotel’s Rakuten Travel page still exists. When the site administrator runs the link check from the plugin’s admin screen, a HEAD request is sent to the hotel’s public page URL (https://travel.rakuten.co.jp/HOTEL/{hotel number}/). Only the hotel number stored for that hotel is included in the URL. No personal data is sent. * Website: https://travel.rakuten.co.jp/ * Terms of Service: https://travel.rakuten.co.jp/info/agreement.html * Privacy Policy: https://privacy.rakuten.co.jp/ Rakuten Affiliate Used to generate affiliate links to Rakuten Travel hotel pages. The Rakuten affiliate ID entered by the user is appended to outbound hotel links. No data is sent to Rakuten Affiliate servers by the plugin itself. * Website: https://affiliate.rakuten.co.jp/ * Terms of Service: https://affiliate.rakuten.co.jp/guideline/ * Privacy Policy: https://privacy.rakuten.co.jp/ Moshimo Affiliate Used to generate Moshimo Affiliate-wrapped links for Rakuten Travel (optional). The Moshimo a_id entered by the user is used to construct outbound links. When a Moshimo a_id is set, a small inline script in each hotel card fires an impression tracking request (1×1 pixel image) to i.moshimo.com so that impressions are counted in the user’s Moshimo report. The request is made by the site visitor’s browser; the plugin itself does not send any data to Moshimo servers. * Website: https://af.moshimo.com/ * Terms of Service: https://af.moshimo.com/af/www/terms/shop * Privacy Policy: https://www.moshimo.co.jp/company/privacy ValueCommerce Used to generate affiliate links for Jalan, Rurubu Travel, Yahoo! Travel, JTB, and Ikyu.com. The ValueCommerce SID and PID entered by the user are used to construct outbound links. No data is sent to ValueCommerce servers by the plugin itself. * Website: https://www.valuecommerce.ne.jp/ * Terms of Service: https://www.valuecommerce.ne.jp/st_affiliate/terms.html * Privacy Policy: https://www.valuecommerce.co.jp/privacy_policy/ Agoda Partner Program Used to generate affiliate links to Agoda hotel pages. The Agoda CID entered by the user is appended to outbound Agoda links. In addition, when the site administrator runs the Agoda link check from the plugin’s admin screen, a HEAD request is sent to Agoda’s public hotel search endpoint (https://www.agoda.com/partners/partnersearch.aspx) to check whether the hotel page exists. Only the Agoda hotel ID stored for that hotel is included in the request. No personal data is sent. * Website: https://partners.agoda.com/ * Terms of Service: https://partners.agoda.com/en-us/terms-and-conditions/ * Privacy Policy: https://www.agoda.com/info/privacy.html Connections to the above services are made only when the user has configured the respective service IDs in the plugin settings.
xpay✦ Agentic Commerce for Publishers
Plugin landing page: https://www.xpay.sh/publishers/wordpress-plugin/ · Documentation: https://docs.xpay.sh/en/publishers/wordpress-plugin · Source code: https://github.com/xpaysh/xpay-agentic-commerce-for-publishers Your readers are increasingly arriving from ChatGPT, Claude, Gemini and Perplexity. They are also still arriving the usual way. xpay✦ Agentic Commerce helps you serve both at once. For human readers, the plugin loads a lightweight recommendation widget (a floating button + a footer drawer) on your connected site — install once, works on every page, no shortcode required. You can narrow the widget to a subset of paths or disable site-wide loading entirely in the settings. For inline placement inside a specific post, use the [xpay_recs] shortcode or the Recommendations Gutenberg block. The plugin never modifies your post content directly — recommendations live in a sandboxed iframe hosted at widget.xpay.sh, sets no third-party cookies, and uses no behavioural targeting. For AI assistants and agents, the plugin publishes a single endpoint at /.well-known/agent-storefront.json that lists products contextually relevant to your site. Agents that fetch it can discover and (where the underlying merchants support it) transact, with the resulting referral attributed back to your site. What it does Site-wide widget (floating button + footer drawer) — loads on every page of your connected site by default. Disable site-wide loading entirely, or narrow it to matching paths only, from Settings → xpay Agentic Commerce → “Where the widget loads”. URL patterns support * wildcards (PostHog-style). Inline placement — shortcode [xpay_recs] and a Gutenberg block for placing a product-card grid inside a specific post. Independent of the site-wide widget. The plugin never modifies post content via the_content — placement is always explicit. Privacy-first — the plugin sets no third-party cookies and emits no tracking pixels. The decision API receives only the public URL, post title, public categories and tags. Personalization is off unless you turn it on and a Consent API plugin reports positive consent. Agent storefront endpoint — publishes /.well-known/agent-storefront.json so AI assistants can list products contextually relevant to the page they are reading. Detects existing .well-known files and refuses to overwrite them. Optional llms.txt augmentation — append a clearly-delimited block to your llms.txt, only if you have opted in. Never replaces an existing llms.txt. Brand-safety controls — exclude product categories and merchant domains directly from the native settings screen. Amazon Associates — set your Amazon Associates tag. Any Amazon link the widget surfaces gets ?tag= appended. Amazon pays you directly. Native WordPress settings screen — all configuration happens inside a standard wp-admin settings page (Settings → xpay Agentic Commerce). No remote UI, no embedded admin iframe. What it does not do It does not modify your post content. The plugin never hooks the_content or rewrites your post bodies. The site-wide widget lives in page chrome (floating button + drawer); inline placement requires an explicit shortcode or block. It does not collect visitor identifiers. The plugin sets no cookies on your site and emits no tracking pixels. It does not change your existing themes, posts or templates. It does not require a merchant relationship. Publishers can install and connect with no e-commerce site of their own. External services This plugin contacts services operated by xpay (xpay.sh). 1. publisher-api.xpay.sh — backend API. POST /storefront/decide — recommendation decision API. The widget iframe (front-end) calls this when it renders. Data sent: page URL, title, categories, tags, site_id. No visitor identifier. POST /storefront/beacon — load/click event endpoint. The widget iframe fires this anonymously when it mounts (load) and when a reader clicks a product card (click). Data sent: site_id, hostname, post URL, merchant domain (on click), user-agent string. No visitor identifier. POST /storefront/register — registration endpoint. Called once from the app.xpay.sh onboard page during one-click connect to mint a site_id. GET /storefront/agent-card/{site_id} — server-to-server call from your WordPress install to build the /.well-known/agent-storefront.json response. GET /storefront/sites — used by the publisher dashboard at app.xpay.sh, not by this plugin. 2. widget.xpay.sh — sandboxed iframe host for the front-end widget. Loaded only on posts where you place the [xpay_recs] shortcode or the Recommendations block, and only when consent allows. Data passed via URL parameters: site_id, post URL, title, public categories, public tags. No visitor identifier. 3. app.xpay.sh — publisher dashboard. Opened in a new tab from the settings page (a button labelled “Open xpay dashboard”). Never embedded. The xpay terms of use and privacy policy: https://www.xpay.sh/legal/terms-of-use/ and https://www.xpay.sh/legal/privacy-policy/. Privacy No third-party cookies, no tracking pixels. The plugin sets no cookies and emits no tracking pixels on your site. Page-context only, no visitor identifiers. The decision API and beacons receive only the public URL of the page, its public title, and its public categories and tags — the same data already in your HTML for search engines. Iframe sandbox isolation. The front-end widget renders inside a sandboxed iframe loaded from widget.xpay.sh. The host page and the iframe are separate browsing contexts that cannot read each other. WP Consent API integration. When the WP Consent API plugin is installed and reports a hard “no” for marketing consent, the widget iframe does not render. All settings stored locally. Your Amazon Associates tag, excluded categories, excluded domains and toggles are stored in WordPress wp_options. They are not copied to xpay’s backend. Cleanup on uninstall. Deleting the plugin removes every wp_options row it created and disables the agent storefront endpoint. Where the recommended products come from The recommendation engine uses a curated catalog of merchants from xpay’s own merchant network, with affiliate-network fallbacks. The agent storefront endpoint only lists products from agent-ready merchants, since those are the only ones an AI assistant can transact with.
