Catalog / p-kachi.jp
65

SEO audit for p-kachi.jp

ピーカチシステム（P+KACHI）｜お店の顧客管理とポイント管理がこれ一つで解決

other

Health 65/100 (fair) · 50 pages crawled · generated 2026-08-26

Download Markdown report (feed to ChatGPT / Claude / Cursor)

ピーカチシステム（P+KACHI）は、飲食店、レストランをはじめ、美容室、リラクゼーション、マッサージ、ネイルサロン、アパレル、温浴施設、クリーニング店など様々な業種業態でご利用いただいている顧客管理／ポイント管理システムです。

50
pages crawled
50
indexable pages
0
errors
288
warnings
696
notices
0
orphan pages
0
broken links
Category breakdown
CategoryScoreErrorsWarningsNotices
Duplicate 69 0 52 49
Canonical 70 0 50 0
Performance 70 0 50 203
Security 70 0 50 100
Agent Readiness 71 0 49 53
Content 78 0 37 50
AI Content 100 0 0 2
Images 100 0 0 50
Robots 100 0 0 1
Sitemap 100 0 0 38
Social 100 0 0 100
Structured Data 100 0 0 50
Findings

Warnings (8 rules)

warning Control has no accessible name

Rule agent.control_no_name · Agent Readiness · 49 occurrence(s)

warning Missing canonical tag

Rule canonical.missing · Canonical · 50 occurrence(s)

warning Thin content (low word count)

Rule content.thin · Content · 37 occurrence(s)

warning Duplicate page content

Rule duplicate.content · Duplicate · 10 occurrence(s)

warning Homepage duplicated across protocol/host variants (no redirect)

Rule duplicate.protocol_host · Duplicate · 1 occurrence(s)

  • https://www.p-kachi.jp/ — https://p-kachi.jp/ serves the same homepage content with a 200 and no redirect — Google sees a duplicate. Pick one canonical host/scheme and 301-redirect the others.

warning Duplicate <title> across pages

Rule duplicate.title · Duplicate · 41 occurrence(s)

warning Content-Type header doesn't match the actual content

Rule headers.content_type_mismatch · Security · 50 occurrence(s)

  • https://p-kachi.jp/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://p-kachi.jp/case/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://p-kachi.jp/case/01.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://p-kachi.jp/case/02.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://p-kachi.jp/case/03.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://p-kachi.jp/case/04.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://p-kachi.jp/case/index.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://p-kachi.jp/faq/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://p-kachi.jp/feature/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://p-kachi.jp/mail/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://p-kachi.jp/point/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://p-kachi.jp/update/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.p-kachi.jp/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.p-kachi.jp/case/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.p-kachi.jp/case/17.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.p-kachi.jp/case/18.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.p-kachi.jp/case/19.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.p-kachi.jp/case/20.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.p-kachi.jp/case/21.html — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.p-kachi.jp/faq/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.p-kachi.jp/feature/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.p-kachi.jp/mail/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.p-kachi.jp/point/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.p-kachi.jp/smaregi/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.p-kachi.jp/update/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".

warning Render-blocking script in <head> (no defer/async)

Rule perf.render_blocking · Performance · 50 occurrence(s)

Notices (20 rules)

notice Heading levels skip a level

Rule agent.heading_skip · Agent Readiness · 2 occurrence(s)

notice No llms.txt for AI agents

Rule agent.llms_txt_missing · Agent Readiness · 1 occurrence(s)

  • https://www.p-kachi.jp/ — no llms.txt found at the site root — add one so AI agents get a curated site summary

notice No main landmark for AI agents

Rule agent.no_main_landmark · Agent Readiness · 50 occurrence(s)

notice Uniform sentence length (scaled-content hygiene signal)

Rule ai.uniform_sentence_length · AI Content · 2 occurrence(s)

  • https://p-kachi.jp/update/ — sentence lengths on this page are unusually uniform (standard deviation 2.3 words, below 4) — a stylistically flat rhythm that correlates with templated or unedited content and low editorial effort. Vary sentence length and add specifics on a re-read. This is a content-quality nudge; it does not determine AI authorship.
  • https://www.p-kachi.jp/update/ — sentence lengths on this page are unusually uniform (standard deviation 2.3 words, below 4) — a stylistically flat rhythm that correlates with templated or unedited content and low editorial effort. Vary sentence length and add specifics on a re-read. This is a content-quality nudge; it does not determine AI authorship.

notice Duplicate meta description across pages

Rule duplicate.meta_desc · Duplicate · 49 occurrence(s)

notice Likely hero image lacks fetchpriority=high

Rule images.hero_no_fetchpriority · Performance · 50 occurrence(s)

  • https://p-kachi.jp/ — the likely hero/LCP image (logo_l.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://p-kachi.jp/case/ — the likely hero/LCP image (logo_l.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://p-kachi.jp/case/01.html — the likely hero/LCP image (logo_l.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://p-kachi.jp/case/02.html — the likely hero/LCP image (logo_l.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://p-kachi.jp/case/03.html — the likely hero/LCP image (logo_l.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://p-kachi.jp/case/04.html — the likely hero/LCP image (logo_l.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://p-kachi.jp/case/index.html — the likely hero/LCP image (logo_l.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://p-kachi.jp/faq/ — the likely hero/LCP image (logo_l.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://p-kachi.jp/feature/ — the likely hero/LCP image (logo_l.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://p-kachi.jp/mail/ — the likely hero/LCP image (logo_l.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://p-kachi.jp/point/ — the likely hero/LCP image (logo_l.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://p-kachi.jp/update/ — the likely hero/LCP image (logo_l.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.p-kachi.jp/ — the likely hero/LCP image (logo_l.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.p-kachi.jp/case/ — the likely hero/LCP image (logo_l.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.p-kachi.jp/case/17.html — the likely hero/LCP image (logo_l.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.p-kachi.jp/case/18.html — the likely hero/LCP image (logo_l.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.p-kachi.jp/case/19.html — the likely hero/LCP image (logo_l.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.p-kachi.jp/case/20.html — the likely hero/LCP image (logo_l.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.p-kachi.jp/case/21.html — the likely hero/LCP image (logo_l.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.p-kachi.jp/faq/ — the likely hero/LCP image (logo_l.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.p-kachi.jp/feature/ — the likely hero/LCP image (logo_l.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.p-kachi.jp/mail/ — the likely hero/LCP image (logo_l.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.p-kachi.jp/point/ — the likely hero/LCP image (logo_l.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.p-kachi.jp/smaregi/ — the likely hero/LCP image (sumaregi.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.p-kachi.jp/update/ — the likely hero/LCP image (logo_l.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.

notice Images without width/height (layout shift / CLS)

Rule images.missing_dimensions · Images · 50 occurrence(s)

notice Legacy <meta name=keywords> tag present (Google ignores it)

Rule meta.keywords_present · Content · 50 occurrence(s)

notice Missing Open Graph tags

Rule og.missing · Social · 50 occurrence(s)

notice Large DOM (over 1500 elements) slows rendering & interaction

Rule perf.dom_size_large · Performance · 2 occurrence(s)

  • https://p-kachi.jp/update/ — the page has 3344 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://www.p-kachi.jp/update/ — the page has 3344 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.

notice Legacy image format (jpg/png/gif) with no next-gen fallback

Rule perf.images_legacy_format · Performance · 50 occurrence(s)

  • https://p-kachi.jp/ — 156 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://p-kachi.jp/case/ — 50 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://p-kachi.jp/case/01.html — 9 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://p-kachi.jp/case/02.html — 9 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://p-kachi.jp/case/03.html — 9 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://p-kachi.jp/case/04.html — 9 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://p-kachi.jp/case/index.html — 50 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://p-kachi.jp/faq/ — 8 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://p-kachi.jp/feature/ — 18 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://p-kachi.jp/mail/ — 8 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://p-kachi.jp/point/ — 51 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://p-kachi.jp/update/ — 8 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.p-kachi.jp/ — 156 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.p-kachi.jp/case/ — 50 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.p-kachi.jp/case/17.html — 9 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.p-kachi.jp/case/18.html — 9 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.p-kachi.jp/case/19.html — 9 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.p-kachi.jp/case/20.html — 12 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.p-kachi.jp/case/21.html — 9 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.p-kachi.jp/faq/ — 8 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.p-kachi.jp/feature/ — 18 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.p-kachi.jp/mail/ — 8 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.p-kachi.jp/point/ — 51 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.p-kachi.jp/smaregi/ — 52 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.p-kachi.jp/update/ — 8 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.

notice No ETag header (no conditional GET for unchanged pages)

Rule perf.no_etag · Performance · 50 occurrence(s)

  • https://p-kachi.jp/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://p-kachi.jp/case/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://p-kachi.jp/case/01.html — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://p-kachi.jp/case/02.html — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://p-kachi.jp/case/03.html — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://p-kachi.jp/case/04.html — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://p-kachi.jp/case/index.html — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://p-kachi.jp/faq/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://p-kachi.jp/feature/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://p-kachi.jp/mail/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://p-kachi.jp/point/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://p-kachi.jp/update/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.p-kachi.jp/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.p-kachi.jp/case/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.p-kachi.jp/case/17.html — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.p-kachi.jp/case/18.html — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.p-kachi.jp/case/19.html — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.p-kachi.jp/case/20.html — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.p-kachi.jp/case/21.html — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.p-kachi.jp/faq/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.p-kachi.jp/feature/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.p-kachi.jp/mail/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.p-kachi.jp/point/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.p-kachi.jp/smaregi/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://www.p-kachi.jp/update/ — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.

notice No Last-Modified header (no conditional GET for unchanged pages)

Rule perf.no_last_modified · Performance · 50 occurrence(s)

  • https://p-kachi.jp/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://p-kachi.jp/case/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://p-kachi.jp/case/01.html — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://p-kachi.jp/case/02.html — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://p-kachi.jp/case/03.html — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://p-kachi.jp/case/04.html — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://p-kachi.jp/case/index.html — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://p-kachi.jp/faq/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://p-kachi.jp/feature/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://p-kachi.jp/mail/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://p-kachi.jp/point/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://p-kachi.jp/update/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.p-kachi.jp/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.p-kachi.jp/case/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.p-kachi.jp/case/17.html — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.p-kachi.jp/case/18.html — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.p-kachi.jp/case/19.html — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.p-kachi.jp/case/20.html — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.p-kachi.jp/case/21.html — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.p-kachi.jp/faq/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.p-kachi.jp/feature/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.p-kachi.jp/mail/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.p-kachi.jp/point/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.p-kachi.jp/smaregi/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.p-kachi.jp/update/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.

notice Slow server response

Rule perf.slow_response · Performance · 1 occurrence(s)

notice robots.txt missing (root returns 404/none)

Rule robots.txt_missing · Robots · 1 occurrence(s)

  • https://www.p-kachi.jp/ — robots.txt did not return a 200 at the site root — a healthy site should serve one (declare your sitemap and confirm the host serves root files)

notice No structured data detected

Rule schema.none · Structured Data · 50 occurrence(s)

notice Missing recommended security headers

Rule security.missing_headers · Security · 50 occurrence(s)

notice target=_blank link without rel=noopener (tab-napping)

Rule security.unsafe_cross_origin_links · Security · 50 occurrence(s)

  • https://p-kachi.jp/ — 23 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://p-kachi.jp/case/ — 13 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://p-kachi.jp/case/01.html — 14 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://p-kachi.jp/case/02.html — 14 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://p-kachi.jp/case/03.html — 14 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://p-kachi.jp/case/04.html — 14 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://p-kachi.jp/case/index.html — 13 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://p-kachi.jp/faq/ — 21 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://p-kachi.jp/feature/ — 13 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://p-kachi.jp/mail/ — 13 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://p-kachi.jp/point/ — 13 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://p-kachi.jp/update/ — 13 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.p-kachi.jp/ — 23 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.p-kachi.jp/case/ — 13 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.p-kachi.jp/case/17.html — 14 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.p-kachi.jp/case/18.html — 13 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.p-kachi.jp/case/19.html — 14 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.p-kachi.jp/case/20.html — 14 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.p-kachi.jp/case/21.html — 14 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.p-kachi.jp/faq/ — 21 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.p-kachi.jp/feature/ — 13 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.p-kachi.jp/mail/ — 13 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.p-kachi.jp/point/ — 13 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.p-kachi.jp/smaregi/ — 10 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.p-kachi.jp/update/ — 13 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".

notice Indexable page not listed in sitemap

Rule sitemap.orphan_not_listed · Sitemap · 38 occurrence(s)

notice Missing Twitter Card tag

Rule twitter.missing · Social · 50 occurrence(s)

Pages (showing 50 of 50)
URLStatusIndexableWordsIn-links
https://p-kachi.jp/
ピーカチシステム（P+KACHI）｜お店の顧客管理とポイント管理がこれ一つで解決		 200 yes 373 30
https://p-kachi.jp/feature/
機能一覧| クラウド型ポイント管理システム ピーカチ		 200 yes 305 30
https://p-kachi.jp/case/
導入事例｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 190 29
https://p-kachi.jp/faq/
よくある質問｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 183 29
https://p-kachi.jp/point/
ポイント機能| クラウド型ポイント管理システム ピーカチ		 200 yes 167 29
https://p-kachi.jp/update/
バージョンアップ情報｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 2015 29
https://www.p-kachi.jp/
ピーカチシステム（P+KACHI）｜お店の顧客管理とポイント管理がこれ一つで解決		 200 yes 373 20
https://www.p-kachi.jp/case/
導入事例｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 190 20
https://www.p-kachi.jp/faq/
よくある質問｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 183 20
https://www.p-kachi.jp/feature/
機能一覧| クラウド型ポイント管理システム ピーカチ		 200 yes 305 20
https://www.p-kachi.jp/point/
ポイント機能| クラウド型ポイント管理システム ピーカチ		 200 yes 167 20
https://www.p-kachi.jp/update/
バージョンアップ情報｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 2015 20
https://p-kachi.jp/case/index.html
導入事例｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 190 21
https://p-kachi.jp/mail/
ステップシナリオ配信| 顧客属性に応じたシナリオステップメール配信ならピーカチシステム		 200 yes 93 2
https://www.p-kachi.jp/mail/
ステップシナリオ配信| 顧客属性に応じたシナリオステップメール配信ならピーカチシステム		 200 yes 93 2
https://p-kachi.jp/case/15.html
導入事例：炭屋 阪南店｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 149 3
https://p-kachi.jp/case/16.html
導入事例：八喜為 新開地南店｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 150 3
https://p-kachi.jp/case/17.html
導入事例：綾髪｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 118 3
https://p-kachi.jp/case/18.html
導入事例：某自動車販売店｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 171 3
https://p-kachi.jp/case/19.html
導入事例：J・マーケット｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 129 3
https://p-kachi.jp/case/20.html
導入事例：うどん料理専門店　八間蔵｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 130 3
https://p-kachi.jp/case/21.html
導入事例：広島菜漬の名店 山豊｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 113 3
https://www.p-kachi.jp/smaregi/
スマレジ連携・顧客管理ポイントシステム│スマレジ × P+KACHI（ピーカチ）│		 200 yes 132 2
https://www.p-kachi.jp/case/15.html
導入事例：炭屋 阪南店｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 149 2
https://www.p-kachi.jp/case/16.html
導入事例：八喜為 新開地南店｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 150 2
https://www.p-kachi.jp/case/17.html
導入事例：綾髪｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 118 2
https://www.p-kachi.jp/case/18.html
導入事例：某自動車販売店｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 171 2
https://www.p-kachi.jp/case/19.html
導入事例：J・マーケット｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 129 2
https://www.p-kachi.jp/case/20.html
導入事例：うどん料理専門店　八間蔵｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 130 2
https://www.p-kachi.jp/case/21.html
導入事例：広島菜漬の名店 山豊｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 113 2
https://p-kachi.jp/case/01.html
導入事例：関村牧場直送和牛 焼肉くらべこ｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 193 2
https://p-kachi.jp/case/02.html
導入事例：心と癒しの森 るり渓温泉｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 265 2
https://p-kachi.jp/case/03.html
導入事例：京風もつ鍋　もつ吉｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 288 2
https://p-kachi.jp/case/04.html
導入事例：ババ・ガンプ・シュリンプ 大阪｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 193 2
https://p-kachi.jp/case/05.html
導入事例：アジアンリゾート スパ・シーレ｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 114 2
https://p-kachi.jp/case/06.html
導入事例：SUITE（スイート）｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 146 2
https://p-kachi.jp/case/07.html
導入事例：手打ち草部うどん のらや｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 148 2
https://p-kachi.jp/case/08.html
導入事例：つけ麺 津気屋｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 205 2
https://p-kachi.jp/case/09.html
導入事例：魚匠 神戸 隆明 北野坂本店｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 305 2
https://p-kachi.jp/case/10.html
導入事例：赤から 和気インター店｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 203 2
https://p-kachi.jp/case/11.html
導入事例：エンジェルコーヒー｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 133 2
https://p-kachi.jp/case/12.html
導入事例：AIMER（エメ）｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 149 2
https://p-kachi.jp/case/13.html
導入事例：ScoLar nara GOOFY｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 168 2
https://p-kachi.jp/case/14.html
導入事例：カルビ屋大福 中央林間店｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 117 2
https://www.p-kachi.jp/case/01.html
導入事例：関村牧場直送和牛 焼肉くらべこ｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 193 1
https://www.p-kachi.jp/case/02.html
導入事例：心と癒しの森 るり渓温泉｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 265 1
https://www.p-kachi.jp/case/03.html
導入事例：京風もつ鍋　もつ吉｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 288 1
https://www.p-kachi.jp/case/04.html
導入事例：ババ・ガンプ・シュリンプ 大阪｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 193 1
https://www.p-kachi.jp/case/05.html
導入事例：アジアンリゾート スパ・シーレ｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 114 1
https://www.p-kachi.jp/case/06.html
導入事例：SUITE（スイート）｜お店の顧客管理とポイント管理システムならピーカチ		 200 yes 146 1

Audit your own site — free

157 checks, internal PageRank, render-diff. No signup, results in ~30s.

Scan your site →