PW Merchant Check misrepresentation readiness score mean

The score turns a broad preparation process into a visible, repeatable checklist. Instead of trying to remember every page, setting and business statement, the store owner can review detected conditions and answer structured questions in one workflow. The result helps identify incomplete areas and provides a practical order for correction.

Its main purpose is prioritisation. If essential contact information is missing, a return policy is inaccessible or a critical declaration cannot be confirmed, the merchant should address that issue before focusing on cosmetic improvements. After making corrections, the review can be run again to measure local progress.

The score is not designed to label a business as trustworthy or untrustworthy. Software cannot establish the truth of every commercial statement. It can detect that an address appears on a page, but it cannot independently prove that the business genuinely operates there. It can find a refund-policy link, but it cannot know whether the merchant consistently follows that policy in real transactions.

Why misrepresentation preparation is broader than product data

Product titles, prices, availability and identifiers matter, but website transparency extends beyond the catalogue. Customers should understand who operates the store, how to contact the business, what they will pay, when an order may arrive, how returns work and what happens at checkout. Information should remain consistent across the homepage, product pages, policy pages, cart, checkout and Merchant Center settings.

A catalogue can contain technically complete products while the store still has serious transparency weaknesses. Conversely, a professional website can have products with missing prices or broken variations. The readiness review therefore considers site-level signals and merchant declarations rather than relying on a single product attribute.

Google’s official misrepresentation policy describes unacceptable practices involving missing relevant information, unavailable offers, misleading claims and unreliable business information. PW Merchant Check uses practical local checks to help merchants prepare, but Google alone applies Google policies and makes account decisions.

How the score is formed

The readiness result is built from two complementary groups of information:

1. Automatic local checks: signals that can be inspected in the WordPress and WooCommerce environment, such as whether expected pages or visible data appear to exist.
2. User declarations: factual questions that require the store owner or an authorised manager to confirm real business practices.

Each completed condition contributes according to the logic of the local checklist. Critical omissions have more practical importance than minor recommendations. The displayed value summarises current answers and detectable signals; it should always be read together with the detailed findings. Two stores with the same percentage may have very different unresolved issues.

For example, one store may lose points because a policy page could not be detected, while another may have an unresolved statement about fulfilment or business identity. The numerical result alone cannot express that difference. Open every finding, confirm its context and correct the underlying cause rather than trying merely to raise the number.

Automatic checks included in the preparation review

Automatic checks examine information available within the site. Depending on the installed version, configuration, theme and WooCommerce structure, the review may look for signals related to:

• HTTPS and basic public accessibility;
• WooCommerce availability and store configuration;
• contact, about, privacy, shipping, return and refund information;
• visible business identity and communication methods;
• cart, checkout and expected store pages;
• product price, stock, image and purchasability conditions;
• consistency risks that deserve manual comparison;
• sample, placeholder or incomplete content signals.

Detection is useful, but it has limits. A policy may be published through a page builder, custom endpoint or multilingual plugin that the scanner does not recognise. An address may exist in an image rather than readable text. A checkout may depend on customer location or an external payment service. A detected page can also contain inadequate or outdated information.

For that reason, every automatic result should be manually verified on the public storefront. Use a private browser window and test both desktop and mobile presentation. A successful technical detection means that a signal was found; it does not prove that the content is accurate, complete or suitable for the intended market.

Why user declarations are necessary

Some facts cannot be established safely from code. The plugin cannot know whether an entered company name matches official records, whether the displayed telephone number is actively answered or whether the merchant truly dispatches orders within the stated period. It cannot prove ownership of product images, validate every commercial claim or observe how refunds are handled after a real sale.

User declarations ask the merchant to stop and confirm these facts. They are not ceremonial boxes to tick. The responsible person should read each question, inspect the live site and select an answer only when there is evidence to support it. If an agency manages the website, the business owner may still need to confirm operational and legal details.

A declaration should remain unanswered or negative when there is uncertainty. That lower score is more useful than an artificially high result built on assumptions. It identifies the work that must be completed before the store presents itself as ready.

What critical questions mean

Critical questions concern foundations of identity, transparency, offer accuracy or normal purchasing. A negative or uncertain answer requires attention before a review request. Examples can include whether customers can identify the seller, contact the business, see truthful prices, understand delivery and return conditions, complete checkout and receive what the store promises.

A critical label inside PW Merchant Check indicates local remediation priority. It does not mean that Google has identified the same issue or suspended the account. The plugin does not connect to Merchant Center, read account diagnostics or receive Google’s internal review data.

When a critical answer is negative, investigate the real operation first and the webpage second. Publishing a sentence that the business cannot honour does not solve a transparency problem. Update the operational process where necessary, then describe it accurately and consistently on the website.

Business identity declarations

A customer should be able to understand which business operates the e-commerce site. Review the business name, trading name, address, telephone number, email address and other relevant registration information used across the site. Compare the homepage, footer, contact page, about page, policy pages, invoices and Merchant Center business settings.

For a store in Türkiye, write the genuine address in a stable format. District, province, postal code and country should not change casually between pages. If a registered office, warehouse and return address are different, label each purpose clearly instead of presenting them as contradictory versions of one address.

Do not mark the identity declaration as complete merely because an address exists somewhere in WordPress administration. Customers must be able to find relevant information on the public website. The information must also represent the actual merchant, not a developer, hosting provider or unrelated supplier.

Contact availability declarations

Confirm that published contact methods work. Send a test message through the contact form, verify delivery to the correct mailbox and check whether replies can be sent. Call the published telephone number during stated operating hours. Confirm that the contact page loads without a login and remains usable on mobile.

A contact method that appears professional but is never monitored can create the wrong expectation. Use realistic support hours and response descriptions. If customer service is provided only in particular languages, markets or hours, explain this clearly.

Shipping and delivery declarations

The merchant must confirm that shipping information reflects actual fulfilment. State available destinations, processing time, estimated transit time, shipping charges and important exclusions. Avoid promising same-day dispatch, free shipping or nationwide delivery unless the store can provide it under the displayed conditions.

Test representative orders from the intended regions. A store targeting İstanbul, Ankara, İzmir, Bursa, Antalya or other locations in Türkiye should verify that the checkout accepts applicable addresses and calculates the expected shipping option. International stores should review each target country’s costs, timeframes and restrictions separately.

Return and refund declarations

A return page should explain the applicable period, eligibility conditions, procedure, address, costs, refund method and expected processing. The merchant must confirm that the published process is actually followed. Do not copy a generic policy containing another company’s details or conditions that conflict with checkout information.

The exact legal requirements vary by jurisdiction and business model. PW Merchant Check is not legal advice and cannot certify compliance with consumer law. Obtain qualified advice where necessary, especially when selling across borders, offering personalised goods or applying product-specific exclusions.

Google provides official guidance for configuring return policies in Merchant Center. Website information and Merchant Center settings should describe the same real process.

Price, availability and checkout declarations

Confirm that product prices are real, current and visible before purchase. A discounted price should apply under the stated conditions. Stock messages must reflect whether customers can order the item. Variable products should display the correct price and availability after the customer selects a size, colour or other option.

Continue into the cart and checkout. Check totals, tax, shipping charges, coupon behaviour, currency and available payment methods. Customers should not discover an unexplained compulsory charge after relying on the product offer. A price stored correctly in WooCommerce is not sufficient if caching, custom code or an external integration shows another value publicly.

Product and claim declarations

Merchants should confirm that products exist, can be supplied as described and are represented with truthful text and images. Claims about authenticity, certification, health effects, guarantees, performance or scarcity require particular care. Remove unsupported superlatives, fake countdowns, fabricated reviews and statements that cannot be demonstrated.

If a catalogue is imported from a supplier, do not assume every title, image and stock value is current. The store remains responsible for what customers see. Review a representative selection manually and prioritise high-value, regulated, heavily advertised and frequently changing products.

Why the score changes

The score can change when the website, WooCommerce data, plugin configuration or declaration answers change. Publishing a missing policy page may improve a detected condition. Removing or renaming a page can make it unavailable to the scanner. Changing an answer from uncertain to verified can affect the result, while acknowledging a newly discovered problem may reduce it.

Theme changes, multilingual routing, maintenance mode, security rules and caching can also affect detection. A policy that loads for an administrator may return an error to a logged-out visitor. A page may be available in Turkish but missing from the English version. Run the review after material site updates and inspect unexpected score movements rather than assuming the plugin is wrong.

A lower result after an honest correction is not a failure. If the merchant discovers that a delivery promise is inaccurate and changes the declaration to negative, the new score more accurately represents the work remaining. Accuracy is more important than preserving a percentage.

What a high score means

A high readiness score means that most local checklist conditions were detected or responsibly confirmed at the time of the scan. It suggests that the store owner has completed a substantial part of the preparation workflow and has fewer visible local gaps to investigate.

It does not mean the store will be approved. Google may evaluate information that PW Merchant Check cannot access, including Merchant Center account configuration, submitted product data, processing results, policy history, linked services and other account-level signals. A high local score also cannot verify that every declaration is true.

Use a high score as a prompt for final manual review, not as permission to skip it. Open the public site as a new customer, place a controlled test order where appropriate, compare key details across channels and ask another person to review the store without relying on internal knowledge.

Why the score is not a Google approval score

PW Merchant Check is developed independently and is not a Google product. It does not use Google’s internal scoring systems, and Google does not publish a universal approval percentage that this plugin could reproduce. The plugin does not send the site for Google review, grant approval or remove an account suspension.

It also works without Google API or OAuth access. Therefore, it cannot read account-level policy issues, product disapprovals, processing statuses or review outcomes. Those must be checked in Merchant Center or through an authorised API-based system.

The mandatory interpretation remains simple: this section is a local readiness indicator based on practical experience; it is not a Google approval score or guarantee.

How to answer declarations responsibly

1. Read the complete question and any explanation shown with it.
2. Open the relevant public page in a logged-out browser.
3. Compare the statement with actual business operations and records.
4. Test contact, shipping, cart or checkout behaviour where relevant.
5. Choose a positive answer only when the statement is currently true.
6. Record uncertainty as unresolved and assign it to the responsible person.
7. Revisit the answer after the correction is live and verified.

Never change an answer solely to improve the score. False confirmation defeats the purpose of the tool and can hide a real customer problem.

Recommended correction order

1. Resolve unclear or contradictory business identity information.
2. Restore working customer contact methods.
3. Fix inaccessible storefront, product, cart and checkout pages.
4. Correct unavailable offers, misleading prices and stock conflicts.
5. Publish accurate shipping, return, refund, privacy and payment information.
6. Test the complete purchase journey on desktop and mobile.
7. Remove unsupported claims, placeholders and copied business details.
8. Re-run site and product audits, then review declarations again.

Preparation checklist before requesting a review

• The public site loads over HTTPS without maintenance mode or access restrictions.
• The seller’s identity and contact information are visible and consistent.
• Contact methods have been tested successfully.
• Shipping destinations, charges and delivery expectations are clear.
• Return and refund conditions describe the real process.
• Privacy, payment and terms information is accessible from mobile and desktop.
• Product prices, currencies, availability and variations are truthful.
• Cart and checkout work for intended customers and regions.
• Sample, demo and copied content has been removed.
• Merchant Center settings and submitted data match the live website.
• Every critical readiness question has been supported with evidence.
• Remaining findings have been reviewed and documented.

Google’s official review-request guidance advises merchants to resolve issues before selecting the review option. Follow the current instructions displayed in the affected Merchant Center account, because available actions and review status are controlled by Google.

When to run the readiness review again

Run it after publishing or materially changing policy pages, contact information, business identity, shipping rules, payment methods, checkout design or a large product update. It is also sensible after changing the theme, page builder, multilingual configuration, security rules or caching system because these can alter public accessibility.

For an active catalogue, use periodic checks as maintenance rather than waiting for a problem. Keep a dated internal record of major corrections and test results. The downloadable HTML report can support this process, but it should not contain inaccurate declarations or be presented as an official Google certificate.

Difference between PW Merchant Check and an API solution

Common mistakes when interpreting the score

• Calling the result a Google score or official certificate;
• ticking declarations without checking the live website;
• focusing on the percentage while ignoring one critical issue;
• assuming that a detected policy page is complete;
• assuming a high score removes the need to inspect Merchant Center diagnostics;
• requesting review before changes are published and tested;
• using the score to promise approval to a client;
• forgetting to review translated or market-specific versions of the store.

Frequently asked questions

Is the readiness score issued by Google?

No. It is calculated locally by PW Merchant Check. The plugin is not developed, approved or certified by Google.

Does 100% guarantee Merchant Center approval?

No. A complete local checklist cannot guarantee Google approval. Google may assess account and product information that the plugin cannot access, and the truth of user declarations remains the merchant’s responsibility.

Does a low score mean my Merchant Center account is suspended?

No. The score is not connected to account status. A site can use the review before creating or connecting any Merchant Center account.

Can PW Merchant Check see the reason for a Google rejection?

No. It has no Merchant Center connection and cannot read Google’s account or product diagnostics. Check the current issue details inside Merchant Center.

Why does the plugin ask questions instead of checking everything automatically?

Software cannot prove many operational facts, such as whether a business answers its telephone, honours refunds or dispatches within its promise. Those points require truthful human confirmation.

Can an agency answer the declarations for a client?

An agency may complete technical checks, but the business owner or an authorised manager should confirm facts about identity, fulfilment, returns, claims and customer service. Do not guess on the client’s behalf.

Why did my score decrease after an update?

A page may have become inaccessible, a setting may have changed, a declaration may have been corrected or the updated review may detect a previously unexamined condition. Compare detailed findings instead of relying only on the total.

Should I add false information to satisfy a check?

Never. Do not invent addresses, telephone numbers, policies, reviews, delivery promises, prices or product identifiers. Correct the real operation and publish accurate information.

How often should I run the review?

Run it after significant site, policy, checkout or catalogue changes and periodically as part of store maintenance. Run it again before a Merchant Center application or re-review.

Does a passed automatic check prove the content is correct?

No. It normally means the expected local signal was detected. Read and test the content manually to confirm accuracy, completeness and public accessibility.

Does the score replace legal advice?

No. It is a technical and practical preparation indicator. Consumer, privacy, tax and distance-selling obligations depend on the applicable jurisdiction and business model.

Is PW Merchant Check free?

Yes. It has no Pro tier, licence code or paid feature restriction. Its local readiness review does not require Google API authorisation.

Are my audit results sent to PW Feed or Poyraz Web?

No. The local site and product checks are not sent to PW Feed or Poyraz Web for analysis. Protect any report you export and share it only with authorised people.

What should I do after reaching a high score?

Complete a final manual storefront test, confirm the truth of declarations, review remaining findings and compare the live site with Merchant Center data. Then follow the review instructions shown in the account if a review is appropriate.

Final assessment

The PW Merchant Check misrepresentation readiness score is most valuable when it is treated as a disciplined checklist, not a promise. It helps WooCommerce merchants see which local transparency signals are present, which facts require human confirmation and which critical areas need correction before a Merchant Center step.

Use the detailed findings, verify every declaration and repeat the review after meaningful changes. Keep the central limitation visible in every decision: this section is a local readiness indicator based on practical experience; it is not a Google approval score or guarantee.

PW Merchant Check is an independent, free preparation tool. It does not connect to Merchant Center, submit products, read Google diagnostics or guarantee approval. Final policy assessment and account decisions belong to Google.