How to Create and Publish a SaaS Listing on the GCP Marketplace with Clazar
Last updated: July 13, 2026
Publishing a SaaS product on the Google Cloud (GCP) Marketplace comes with its own set of rules — tight character limits, plain-text descriptions, a mandatory tax classification, and a required login URL that shapes the buyer's very first post-purchase moment. This standalone guide walks through every section and field required to create and publish a SaaS listing on the GCP Marketplace via Clazar, with field-by-field instructions, character limits, tips, and best practices for each, covering all GCP-specific fields and requirements.
Throughout the guide, fields carry one of three status markers:
Compulsory — mandatory. The listing cannot be submitted without completing this field.
Optional — not required, but highly recommended for better discoverability and buyer engagement.
Optional (Recommended) — not mandatory, but strongly advised to maximise your listing's visibility and conversion.
Section 1: General Information
The General Information section defines your product's core identity on the GCP Marketplace — the first details buyers see when browsing. All three fields here directly impact your listing's discoverability, brand impression, and click-through rate, so complete this section accurately and professionally, as it forms the face of your product on the marketplace.
1.1 Listing Title — Compulsory
The Listing Title (up to 64 characters) is the primary name that appears on your GCP Marketplace product page and the most prominent text buyers see when searching or browsing. The placeholder text notes that your listing title will be used to list your SaaS on the marketplace. It must be concise, clear, and accurately reflect what your product does, ideally including your product or company name and hinting at the product's core function or value. GCP enforces a strict 64-character limit — significantly shorter than many other marketplaces — so precision is critical.
Include your product or brand name prominently at the start, and add a short descriptor that captures the product category (e.g., "by CompanyName"). Avoid generic words like "software" or "platform" without context, don't use ALL CAPS or excessive punctuation, and keep the title within 50–64 characters for the best display across devices.
Example: "DataSync Pro — Real-Time Integration by Acme" (47 characters)
1.2 Short Description — Optional
The Short Description (up to 100 characters) is a brief tagline displayed alongside your listing title in GCP Marketplace search results and category pages. The placeholder describes it as a short snippet about your product, shown when users are browsing the Marketplace. Although optional, it's the second piece of text buyers read before deciding to click, and a well-crafted one dramatically improves click-through rates and filters in relevant buyers. Communicate your product's core value in one punchy sentence, using plain, non-technical language a decision-maker can grasp at a glance.
Write a single, compelling sentence that captures your primary value proposition, and lead with the benefit (what the buyer gains) rather than just what the product does. Use active language and present tense, avoid repeating the product title, and don't exceed 100 characters including spaces.
Example: "Automate data pipelines across 200+ cloud sources in minutes, with zero code." (83 characters)
1.3 Listing Logo — Compulsory
The Listing Logo is your product's visual brand identifier, appearing prominently on your listing page, in search results, and in category listings. GCP enforces strict specifications: the image must be PNG only, square (1:1 aspect ratio), between 130 px and 512 px (width and height equal), and no larger than 256 KB. The upload will be rejected if any of these requirements aren't met.
Use your official product or company logo, ideally at 512 × 512 px for maximum clarity, with a transparent or white background for a clean presentation. Keep the file size under 256 KB (compress if needed using tools like TinyPNG), don't use JPG, GIF, SVG, or any format other than PNG, and ensure the logo remains legible and recognisable at small sizes, since it may display as small as 130 px.
Section 2: Listing Overview
The Listing Overview section is where you provide the detailed written content that appears on your full GCP Marketplace product page — your primary sales copy visible to all prospective buyers. The Long Description is the most impactful field in your entire listing. You'll also define your product's unique URL segment, which forms part of your permanent GCP Marketplace listing URL. Fill in every field thoughtfully, as this section heavily influences buyer decisions.
2.1 Long Description — Optional (Recommended)
The Long Description (up to 4,096 characters) is the full product narrative displayed on your product page, and it's your most important piece of marketing content — buyers who click through read this to decide whether to purchase or enquire. While it isn't form-required on Clazar, it's strongly recommended for GCP Marketplace quality. It should cover what your product does, who it's for, the key problems it solves, its core features and benefits, and any notable technical integrations. The placeholder describes it as the product overview shown on your Marketplace page, highlighting the content and capabilities of your product.
A strong structure runs from an opening paragraph (2–3 sentences describing what your product does and who benefits), through a problem statement (the core challenges you solve), a key features list (5–8 benefit-oriented highlights), use cases (2–3 specific scenarios or industries where you deliver value), a note on GCP compatibility (how your product integrates with or complements Google Cloud services), and a closing call to action (a clear next step such as visiting your website, starting a trial, or contacting sales). A recommended length of 2,000–3,500 characters makes for a comprehensive, informative listing.
⚠ Important: GCP Marketplace accepts plain text only — no HTML, markdown, or rich text formatting. Use clear paragraph breaks for readability, and avoid special characters or symbols that may render incorrectly.
2.2 Product Info Link — Optional
The Product Info Link (up to 2,048 characters) is an external URL pointing buyers to a detailed product information page — typically your main product website, a dedicated landing page, or your documentation hub. The placeholder describes it as a link to detailed information, such as your product's website. It appears on your listing page and gives interested buyers an easy way to learn more before committing. Although optional, it's strongly recommended, as it extends the buyer journey beyond the marketplace and lets you capture leads and conversions on your own platform.
Link to your primary product page or a dedicated GCP Marketplace landing page, using HTTPS URLs only for security and credibility. Make sure the linked page is publicly accessible (no login required), loads quickly, and is mobile-friendly, and avoid linking to internal tools or password-protected pages.
Example: https://www.yourcompany.com/gcp-marketplace
2.3 URL Segment — Compulsory
The URL Segment (up to 48 characters) is a unique identifier that becomes part of your GCP Marketplace listing URL. It's appended to the base marketplace URL to form your product's permanent web address (e.g., console.cloud.google.com/marketplace/product/[your-url-segment]). The placeholder notes that a custom URL segment will be appended to your product's URL on the marketplace, with the example "company-name." Choose it carefully, as it directly impacts the shareability and SEO of your listing URL, and keep it in a clean, lowercase, hyphen-separated format that reflects your product or brand name.
Use lowercase letters and hyphens only (no spaces, underscores, or special characters), keep it short and memorable (ideally under 30 characters), and match it to your product or company name for brand consistency. Check that it's unique and not already in use on GCP Marketplace, and avoid version numbers or dates, which may become outdated.
Example: "acme-datasync-pro" (18 characters)
Section 3: Pricing Plan
The Pricing Plan section defines how buyers are charged for your product. At least one pricing plan is required before you can publish. GCP Marketplace supports multiple plan types — Free, Flat Fee, Usage Based, and a combined Flat Fee & Usage Based model — and you can create multiple plans for buyers to choose from at purchase. Plans can be set to private (hidden from public view) or public. Each plan needs a unique identifier, a display title, and a pricing model selection.
3.1 Plan ID — Compulsory
The Plan ID is a unique internal identifier for each pricing plan, used by Clazar and GCP to distinguish between the plans you offer (its placeholder is simply "Unique Plan ID"). It isn't typically visible to buyers on the marketplace front-end but is used in backend processes and API references. Each plan must have a distinct Plan ID, so use a clear, consistent naming convention that reflects the plan tier or type.
Use alphanumeric characters and hyphens (no spaces or special characters), apply a consistent naming scheme across all plans (e.g., plan-starter, plan-professional, plan-enterprise), keep it short and descriptive, and ensure each plan's ID is unique across your listing.
Example: "gcp-plan-starter", "gcp-plan-pro", "gcp-plan-enterprise"
3.2 Plan Title — Compulsory
The Plan Title is the buyer-facing name of your pricing plan displayed on the GCP Marketplace (placeholder: "Plan Title"). When buyers arrive at your listing, they see a list of available plans with this title, so it should be clear, professional, and immediately convey the tier or type of plan. It's often the first thing buyers look at when comparing plans, so use names that are intuitive and easy to understand.
Use standard SaaS tier naming conventions such as Starter, Professional, Business, or Enterprise — or describe the plan by its value, like Free Tier, Pay-As-You-Go, or Annual Commitment. Keep it concise and easy to compare when multiple plans are listed.
Example: "Starter Plan", "Professional Plan", "Enterprise Plan"
3.3 Pricing Option — Compulsory
The Pricing Option, selected from a dropdown, determines the billing model GCP Marketplace applies when a buyer subscribes to this plan. This is a critical business decision that defines how you monetise your product, so choose the model that best aligns with your existing pricing structure and is most intuitive and attractive to your target buyers. The available options are:
Free — Your product is available at no charge. No billing integration required. Choose this for a trial, freemium tier, or evaluation version.
Flat Fee — Buyers are charged a fixed recurring amount (monthly or annually) regardless of usage. Best for subscription-based SaaS with predictable pricing.
Usage Based — Buyers are charged based on actual consumption (e.g., per API call, per GB, per user). Best for pay-as-you-go or consumption-driven services.
Flat Fee & Usage Based — A combination model with a fixed base fee plus variable usage charges on top. Choose this when you have a base subscription with metered overages.
You can create multiple plans with different pricing options to cater to different buyer segments.
3.4 Private Plan (Visibility Setting) — Optional
The Private checkbox (set per plan, unchecked by default so plans are public) lets you make a specific pricing plan invisible to the general public on the GCP Marketplace. When a plan is marked private, it won't appear in the list of available plans shown to regular browsing buyers. Private plans are typically used for enterprise custom pricing, exclusive partner deals, or negotiated contracts — only buyers explicitly granted access (e.g., via a private offer or direct link) can see and subscribe to them.
Leave the box unchecked for all standard, publicly available plans, and check it for enterprise or negotiated plans that shouldn't be publicly displayed. You can have a mix of public and private plans in the same listing.
Note: To add additional plans, click the "+Add Pricing Plan" button below the current plan.
Section 4: Features
The Features section is unique to GCP Marketplace. It lets you define a structured list of features for each pricing plan, making it easy for buyers to compare what's included in each. At least one feature is required per pricing plan. Features are displayed in a visible comparison table on the listing, helping buyers make informed decisions, and each feature can be associated with specific plans and optionally include a tooltip for extra explanation.
4.1 Feature Name — Compulsory (at least one per plan)
The Feature Name (displayed as "Feature 1", "Feature 2", and so on) is the label for a specific capability or attribute of your product shown to buyers on the listing page. Features appear in a structured comparison format so buyers can see which are available in each plan, and at least one feature must be added per plan before you can proceed. Feature names should be short, descriptive, and benefit-oriented — they're visible to the public and should communicate value clearly.
Use short, punchy feature names (2–6 words each), and focus on capabilities buyers care about, such as storage limits, user seats, API access, SLA, or priority support. Aim for 5–10 features per plan for a comprehensive comparison, and use consistent terminology across all plans for easy comparison.
Examples: "Unlimited Storage", "Priority Support", "API Access", "Up to 10 Users", "99.9% SLA Guarantee", "Custom Integrations"
4.2 Feature Tooltip — Optional
The Feature Tooltip (shown as "This is text for tooltip") is an optional short description that appears when a buyer hovers over or clicks a feature name in the comparison table. It provides extra context about what a feature means or includes — especially useful for technical features, limits, or terms buyers may not immediately understand from the name alone. Adding tooltips improves transparency and builds buyer confidence.
Keep tooltips to one or two sentences maximum for readability, use them to clarify limits, conditions, or technical details, and avoid repeating the feature name verbatim.
Example — Feature: "API Access" | Tooltip: "Full REST API access with up to 10,000 calls per day. Rate limits apply on the Starter plan."
4.3 Plan Association — Compulsory (per feature)
The Plan Association dropdown (which defaults to "NA") links each feature to the specific pricing plan(s) it belongs to. When you have multiple plans, this field tells GCP Marketplace which plans include a particular feature, driving the comparison table shown to buyers. Each feature can be associated with one or multiple plans — features not associated with a plan will show as "NA" and may not display correctly in the comparison table.
Always associate each feature with at least one plan. For features available across all plans, associate them with all plans, and use plan-specific features to differentiate tiers (e.g., "Priority Support" only for the Enterprise plan).
Note: To add additional features, click the "+Add New Feature" button below the current feature row.
Section 5: Legal
The Legal section covers all licensing, compliance, and tax-related information required by GCP Marketplace, including the End User License Agreement (EULA), any additional licence agreements, and the Tax Category classification. Review all fields carefully with your legal and finance teams before submission. The Tax Category field is mandatory and unique to GCP Marketplace, as it determines how Google classifies your product for tax reporting purposes.
5.1 End User License Agreement (EULA) — Compulsory
The EULA defines the legal terms under which buyers may use your product purchased through GCP Marketplace, and every listing must have one. Selected via radio button, you have two options:
Standard contract from Google — You accept Google's standard terms and conditions as the governing EULA. This is the fastest and simplest option, pre-approved and convenient.
Custom EULA — You upload or provide your own EULA document, which governs the legal relationship between you and the buyer.
If you don't have a specific EULA requirement, use the Standard contract from Google for simplicity. If you choose a Custom EULA, have your legal team draft and review it before submission, ensure it doesn't conflict with Google's marketplace policies, and make sure it covers usage rights, restrictions, data handling, liability, and termination clauses.
5.2 Additional License Agreements — Optional
The Additional License Agreements field lets you attach supplementary legal documents beyond the primary EULA — the sub-label prompts you to include any additional license agreements that apply to this product. These could include data processing agreements (DPAs), open-source licence notices, third-party component licences, accessibility agreements, or any product-specific terms buyers must acknowledge in addition to the main EULA. It's optional but should be used whenever your product incorporates third-party software or has specific compliance requirements.
Include a Data Processing Agreement (DPA) if your product processes buyer or end-user personal data, and add open-source licence notices if your product uses OSS components. Use "+ Add Additional Licence Agreement" to add multiple agreement links, and host each additional agreement at a stable public URL.
5.3 Tax Category — Compulsory
The Tax Category is a required field unique to GCP Marketplace, selected via radio button under the sub-label "Select if your solution primarily:". Google uses this classification to determine the correct tax treatment for your product across jurisdictions, so you must select the single option that most accurately describes your product's primary function. The choice affects how Google taxes marketplace transactions in applicable countries and regions — consult your finance or tax team if you're unsure. The five options are:
Provides data mining, data analysis, or business analytics capabilities — select this for BI tools, analytics dashboards, and reporting platforms.
Aggregates and classifies data — select this for data catalogues, MDM tools, and data enrichment services.
Provides security/firewall or cloud data storage — select this for security software, firewalls, and cloud backup products.
Is a support plan — select this if you're selling a managed support or maintenance service.
Is none of the above — select this for general SaaS products, CRMs, project management tools, and communication platforms.
⚠ Important: This field cannot be left blank. Choose the most accurate option based on your product's primary function, and consult your finance/legal team if in doubt.
Section 6: Support
The Support section gives buyers all the information they need to get help with your product after purchase — links to tutorials and documentation, a general support description, a support URL, and the critical Login URL. The Login URL is the only required field in this section and is unique to GCP Marketplace: buyers use it to access your product after subscribing. Completing this section fully reduces buyer friction and improves customer satisfaction.
6.1 Tutorials and Documentation — Optional (Recommended)
This field lets you add one or more links to your product documentation, tutorials, video guides, FAQs, user manuals, or other educational resources — you add each via "+Add Tutorial and Documentation," and the sub-label prompts you to add links to your product's documentation and additional resources such as videos and FAQs. These links appear on your listing page under a support/resources section, helping buyers self-serve their onboarding and reducing the burden on your support team. Well-documented products also build trust and increase conversion.
Link to your main documentation hub or knowledge base, add Quick Start guides, Getting Started tutorials, or video walkthroughs, and include an FAQ page link if available. Use publicly accessible HTTPS URLs, and aim to add at least two or three resource links for a well-rounded support section.
6.2 Support Description — Optional
The Support Description (up to 2,048 characters) is a free-text field where you describe the support channels and response standards available to buyers (placeholder: "Details about the type of support provided by you"). It appears on your listing page and helps buyers understand what support to expect after subscribing, increasing confidence and reducing pre-purchase hesitation. Cover your support channels, availability hours, response times, and escalation process.
List your support channels (email, live chat, phone, Slack, ticketing system), and state your support hours and time zone (e.g., 24/7, or Monday–Friday 9am–6pm EST). Mention guaranteed response times (e.g., critical issues within 1 hour, general queries within 24 hours), reference plan-specific support tiers if they differ, and aim for a concise, informative 200–500 characters.
6.3 Support URL — Optional
The Support URL (up to 2,048 characters) links directly to your customer support portal, help centre, or support contact page (placeholder: "URL of your support page"). Displayed on your listing, it gives buyers a direct path to reach your team. Although optional, it's highly recommended, as it supports post-purchase satisfaction and reduces churn by ensuring buyers can easily find help.
Link to your primary support or help centre URL (e.g., support.yourcompany.com), use HTTPS, and ensure the page is publicly accessible without login. If you have a dedicated GCP customer support page, use that specific URL.
Example: https://support.yourcompany.com or https://help.yourcompany.com
6.4 Login URL — Compulsory
The Login URL (up to 2,048 characters) is the direct URL to your product's login page, and it's a required field unique to GCP Marketplace (placeholder: "Login of your product which the buyers will use to login"). After a buyer successfully subscribes through the marketplace, GCP directs them to this URL so they can log into your application and start using it. This is critical for the post-purchase experience — if the URL is incorrect, broken, or leads to an error, buyers face immediate onboarding issues that can lead to cancellations and negative reviews.
Provide the exact URL of your product's sign-in page, use HTTPS, and ensure the URL is stable and won't change after the listing goes live. Test the login URL before submission to confirm it loads correctly, and if your product supports SSO with Google, configure this first so buyers can log in with their Google credentials. Do not use a landing page or marketing page — it must be the actual login/sign-in page.
Example: https://app.yourcompany.com/login or https://auth.yourcompany.com/signin
Section 7: Categories & Keywords
The Categories & Keywords section determines where and how your product appears in GCP Marketplace searches and category browsing. Choosing the right categories ensures your listing is shown to buyers searching in the correct areas, while keywords let you capture additional search terms buyers might use. This section directly impacts your listing's organic discoverability.
7.1 Categories — Compulsory
Categories define which sections of the GCP Marketplace your product appears in. GCP uses a flat category structure — a single dropdown list, unlike other marketplaces that use hierarchical primary/secondary category trees. You can select up to 4 categories (at least one is required), and choosing the most accurate and relevant ones ensures your product is found by the right buyers browsing category pages.
Select your primary category first — the one that best describes your product's core function — then add up to three secondary categories that reflect adjacent use cases or buyer segments. Don't select irrelevant categories just to gain broader exposure, as this can reduce listing quality and buyer satisfaction. Common GCP category examples include Analytics, Business Intelligence, Collaboration, Data Management, Developer Tools, Security, and Storage. Review all available categories in the dropdown before making your selections.
7.2 Keywords — Optional (Recommended)
Keywords are search terms GCP Marketplace uses to match your listing with buyer search queries. You can add up to 150 keywords, entered as comma-separated values in a single text area (the placeholder confirms a maximum of 150 keywords). Keywords aren't publicly visible to buyers but are indexed by the marketplace's search engine, so a well-researched list significantly improves organic search visibility and drives more qualified traffic to your product page.
Include your core product category terms (e.g., data integration, cloud analytics, CRM) and GCP-specific terms (e.g., BigQuery integration, Google Cloud Storage, GCP connector). Add industry-specific terms relevant to your audience (e.g., fintech, healthcare, e-commerce), common synonyms and variations of your key capabilities, and a mix of short-tail (single word) and long-tail (multi-word phrase) keywords. Separate each keyword or phrase with a comma and a space, and review and update them periodically to reflect new features or market trends.
Example keyword list (partial): data integration, ETL, cloud connector, pipeline automation, real-time sync, Google Cloud, BigQuery, business intelligence, SaaS integration, API connector, no-code ETL, data warehouse
Section 8: Finish Up — Pre-Submission Checklist
The Finish Up section is the final review gate in Clazar before your listing can be submitted to GCP Marketplace for review. You won't be able to submit until all compulsory fields across all sections are completed. Use this checklist to ensure your listing is complete, accurate, and ready.
Section 1 — General Information:
[ ] Listing Title entered (max 64 characters)
[ ] Short Description written (max 100 characters) — recommended
[ ] Logo uploaded (PNG, square 1:1, 130–512 px, max 256 KB)
Section 2 — Listing Overview:
[ ] Long Description written (max 4,096 characters, plain text only)
[ ] Product Info Link added (HTTPS URL) — recommended
[ ] URL Segment defined (max 48 characters, lowercase, hyphens only)
Section 3 — Pricing Plan (at least 1 plan required):
[ ] Plan ID created (unique, no spaces)
[ ] Plan Title written (buyer-facing name)
[ ] Pricing Option selected (Free / Flat Fee / Usage Based / Flat Fee & Usage Based)
[ ] Private checkbox set correctly (unchecked = public, checked = private)
Section 4 — Features (at least 1 feature per plan required):
[ ] At least one Feature Name added per plan
[ ] Feature Tooltips added for complex features — recommended
[ ] Each feature associated with the correct plan(s)
Section 5 — Legal:
[ ] EULA selected (Standard Google contract or Custom EULA)
[ ] Additional License Agreements added if applicable
[ ] Tax Category selected (one of the 5 required options)
Section 6 — Support:
[ ] Tutorials and Documentation links added — recommended
[ ] Support Description written (max 2,048 characters) — recommended
[ ] Support URL entered (HTTPS URL) — recommended
[ ] Login URL entered (HTTPS URL, tested and working) — required
Section 7 — Categories & Keywords:
[ ] At least one Category selected (up to 4 allowed)
[ ] Keywords added as comma-separated values (up to 150) — recommended
Before you submit:
Preview your listing using the Preview button in Clazar to see how it will appear to buyers on GCP Marketplace. Test your Login URL in an incognito browser window to confirm it loads correctly, and proofread all text for spelling errors, grammatical mistakes, and formatting issues. Confirm the Tax Category selection with your finance or legal team, verify your EULA covers all usage terms and complies with GCP Marketplace policies, and ensure your listing logo file is PNG format, 1:1 ratio, 130–512 px, and under 256 KB.
For the complete, always-up-to-date version of these guidelines — including any additional notes and examples — refer to the full document here: