Use EXPLAIN and PROFILE in Neo4j Cypher to diagnose slow queries and ensure index-backed lookups

Steps

1. Prefix a query with EXPLAIN to retrieve the logical execution plan without running it: EXPLAIN MATCH (u:User {email: $email}) RETURN u — inspect for NodeIndexSeek vs NodeByLabelScan operators
2. Prefix with PROFILE to execute the query and collect runtime statistics: PROFILE MATCH (u:User)-[:FOLLOWS]->(f) WHERE u.email = $email RETURN f — check db hits and rows per operator
3. If the plan shows NodeByLabelScan instead of NodeIndexSeek, create a property index: CREATE INDEX user_email_idx FOR (u:User) ON (u.email) and re-run EXPLAIN
4. For composite lookups create a composite index: CREATE INDEX FOR (u:User) ON (u.email, u.status) — Cypher uses it only when both properties appear in the WHERE clause
5. Inspect the profile output for high db-hits operators; rewrite the query to push selective filters earlier in the MATCH pattern to reduce the candidate set
6. Use query hints (USING INDEX u:User(email)) to force a specific index when the planner chooses a suboptimal plan